spawn-dock creates a separate Docker environment for each repository, issue, or PR.
By default, projects reside in ~/.spawn-dock.
- Docker Engine or Docker Desktop
- Docker access without
sudo - Node.js and
npm
npm i -g @spawn-dock/cli
spawn-dock --helpspawn-dock auth github login --web
spawn-dock auth codex login --web
spawn-dock auth claude login --webYou can pass a link to a repository, branch (/tree/...), issue, or PR.
spawn-dock clone https://github.com/SpawnDock/cli/issues/122 --force --mcp-playwright--forcerecreates the environment and removes the project's volumes.--mcp-playwrightenables Playwright MCP and the Chromium sidecar for browser automation.
Automatic agent launch:
spawn-dock clone https://github.com/SpawnDock/cli/issues/122 --force --auto--autoselects Claude or Codex based on available authentication. If both are available, the choice is random.--auto=claudeor--auto=codexforces a specific agent.- In auto mode the agent executes the task on its own, creates a PR, and the container is cleaned up after completion.
spawn-dock --help
This workspace also includes a separate package @spawn-dock/cli for bootstrapped
SpawnDock TMA projects.
It runs inside a directory that already contains spawndock.config.json and
defaults to launching opencode. The runtime can be overridden via
SPAWNDOCK_AGENT_RUNTIME=codex|claude|opencode or via agentRuntime in
spawndock.config.json.
This is an intentionally minimal launcher. It locks the project root and launches
the agent only from it; opencode by default starts via
codex sandbox linux, and codex itself launches with workspace-write sandbox.