Delegate work to an isolated sandbox container — launch Claude in Docker to autonomously work on GitHub issues, PRs, or freeform tasks, then monitor progress and report back
Use this skill when the user asks you to run work in a sandbox, or when you recognize a task that would benefit from isolated autonomous execution (long-running issue work, untrusted code, tasks that can run independently).
If suggesting proactively: Explain why a sandbox would be appropriate and ask for confirmation before launching.
Before launching, verify:
claude-sandbox --help (see CLI Reference below). If it fails, tell user: "Plugin not found. Try restarting Claude Code or check that the plugin is installed."git remote get-url origin in the current working directory. If it fails, tell the user: "Not in a git repository with a remote. Navigate to a repo first."To keep displayed commands clean, define a shell function in each Bash tool call:
claude-sandbox() { "${CLAUDE_PLUGIN_ROOT}/claude-sandbox" "$@"; }
Then invoke commands as claude-sandbox <command> [flags]. Always set the Bash tool description to a short, human-readable form (e.g., claude-sandbox run --repo org/repo) so the user sees a clean invocation instead of the full plugin path.
Example Bash tool call: