Run Claude Code autonomously,
without risking your machine
claude-forge runs Claude Code with full autonomy inside an isolated
Docker container — it reaches only your project and what you allow.
Isolated by default
Claude Code runs with --dangerously-skip-permissions — but inside a container, where the worst it can touch is the project you mounted, never your host.
One command, whole environment
claude-forge start wires up the session network, gateway, and MCP sidecars, and tears them down again — list, resume, and prune manage the container environments for you.
Your tools keep working
Sandboxing usually breaks an agent’s tooling. Here GitHub operations work out of the box via a repo-scoped MCP server, first-party Kubernetes and Google Cloud servers ship in the repo, and your own MCP servers plug in via config.
Docker-in-Docker, opt-in
Give sessions their own isolated Docker daemon for building and running containers — with no view of the host’s containers.
Zero setup inside the sandbox
No re-configuring a fresh container every run: your git identity, Claude Code login, plugins, and dependency caches are carried in automatically, so sessions behave like your own machine.