See Sandbox State Before Acting
The Explorer tree and status bar expose live sandbox state. Actions are state-gated, and long-running operations stream into the extension log.
- Live status
- State-gated actions
- Streamed operation log
Open source · VS Code extension
Sandbox Console
Keep coding agents off the host while preserving a native VS Code workflow. Sandbox Console runs each agent inside an isolated Docker Sandbox microVM, with repository-owned lifecycle and access boundaries.
How the Boundary Works
Fast agent execution stays useful when the environment, credentials and lifecycle remain explicit.
- Isolation
- The agent runs inside a Docker Sandbox microVM while the repository workspace stays mounted into that boundary.
- Recipe
- Each sandbox is declared in a committed
.sandbox/config.yamlfile, so the environment changes with the code. - Lifecycle
- Setup, startup and background service hooks are declared once and replayed at the right point in every sandbox run.
- Automation
- A generated
.sandbox/scripts/sbx.shexposes the same sandbox model to people, scripts and headless agent tasks.
What Stays Inspectable
Commit the Recipe, Keep Machine State Local
The recipe and generated CLI are committed. The machine identity, generated kits and cached credentials stay outside version control.
- Committed configuration
- Gitignored local state
- Generated project CLI
Keep Credentials Out of Git and Shell History
Selected credentials travel over standard input to the sandbox secret store, leaving the repository, image and shell history free of credential values.
- Standard-input transfer
- Per-sandbox secrets
- Repository stays clean
Source, architecture notes and the security policy are public in the Sandbox Console repository.