Crabbox CLI
Warms an isolated box, syncs your working diff into it and runs the suite without touching your machine
- 1,532 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Moves code into an isolated or remote box
- Runs commands and tests that execute code
Install
- Works in
Manual install
brew install openclaw/tap/crabboxFull distribution with companion files.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Moves code into an isolated or remote box
- Runs commands and tests that execute code
This is third-party code. Review the repository files before installing.
What it does
Crabbox spins up a pre-warmed isolated box, syncs the current diff from your working copy into it and runs commands and tests there. This way checks happen in a clean environment while your machine stays free. It ships with skills: a quickstart and an automatic review of changes. It installs via Homebrew or go install, and the skills are added with a separate command.
Who it is for. For developers and devops engineers who need to run tests and commands in a clean isolated environment.
Good fit when
- You need to run tests in a clean environment without tying up your machine
- You want to check changes before commit in isolation
- You need an automatic review of changes
Not a fit when
- Running tests locally is enough
- You cannot move code into an isolated or remote box
Example request
Run this project's tests through Crabbox in an isolated box and show the resultLimitations
Boxes can be spun up locally or with third-party providers, whose availability and cost you should consider. Installing via go install builds only the CLI without some companion files, while Homebrew gives the full distribution.
How to disable. Remove crabbox with brew uninstall or delete the built binary and remove the added skills.
FAQ
Where is the box created?
Locally or with supported sandbox providers; the choice depends on configuration.
How does go install differ?
It builds only the CLI without some companion files and assets; Homebrew gives the full distribution.
Discussion
No questions or reviews yet.
Related
CLI toolsAgentBox runs Claude Code, Codex and Open Code in separate virtual machines on your PC, a self-hosted server or a cloud.
Runs each agent stage in its own micro-VM: Claude, Codex, Ollama or any CLI, with OTLP tracing
A CLI that runs Claude Code and Codex in isolated Docker containers with a firewall, worktrees and a no-Dockerfile image.
A Docker sandbox for coding agents: a Debian image with Copilot CLI, Codex and Pi, and SSH, RDP and Docker enabled by flags.
ExitBox runs Claude, Codex, Cursor and other agents in rootless containers: a domain allowlist and secrets in an encrypted vault.
ArcBox runs Claude Code in a disposable microVM on a Mac: its own kernel, an empty workspace and a start in about a second
README in short
The README describes Crabbox as a tool that warms an isolated box, syncs the current diff into it and runs commands and tests. Installation is via Homebrew for the full distribution or go install for the CLI only. It ships with quickstart and automatic change-review skills added via npx skills add. It shows running commands in the box.