One project, one sandbox
sbxm gives every registered GitHub project its own Docker Sandbox and keeps the host clone and project metadata together.
A Docker Sandbox for every GitHub project.
sbxm prepares an isolated Docker Sandbox, a host clone, and predictable Git worktrees so each project has a guarded place to work.
Install
brew install crescware/tap/sbxmStart
sbxm status –global
sbxm add git@github.com:<owner>/<repository>.gitA guarded project workflow
Section titled “A guarded project workflow”Predictable worktrees
Use an attached worktree or create up to 32 detached worktrees for independent agents and tasks.
Credentials stay outside
GitHub credentials use Docker Sandboxes’ secret proxy. The real token is not copied into the sandbox.
A guarded lifecycle
Register, prepare, open, inspect, rebuild, stop, and destroy projects with explicit safety checks.
What sbxm keeps separate
Section titled “What sbxm keeps separate”HostClone, Dockerfile, metadata, and registry remain on the host.
SandboxRepository setup and managed worktrees live inside the Docker Sandbox.
ProxyThe secret proxy supplies GitHub credentials only to registered hosts.
Built for the supported host
Section titled “Built for the supported host”sbxm currently targets macOS 14 or later on Apple silicon with Docker Desktop, Docker Sandboxes CLI 0.37.0 or later, Git, SSH, and a repository-scoped GitHub personal access token.
Read the requirementsConfirm the host, Docker, Git, SSH, and GitHub prerequisites.
Follow the quick startRegister a project, set its credential, prepare it, and open the sandbox.
Keep the source close
Section titled “Keep the source close”sbxm is open source under the MIT License. Read the README on GitHub, browse the source, or see the latest releases.