AGRO
AGRO gives coding agents an isolated Docker sandbox that you control. Two or more agents can work side by side in one sandbox, for example Claude Code, Codex, and Pi. See the harness overview for every supported harness. The sandbox keeps the agents, their tools, and their logins off your host. The sandbox runs on your laptop or on a remote VM, and the agents keep working after you disconnect.
What AGRO gives you
- One CLI.
agrocreates, starts, stops, and removes each sandbox. - A clean host. The host needs Docker, Git, and Node.js ≥ 20. Node runs the
agroCLI only. See Installation. - A persistent home. Logins, tools, and the workspace live in one volume that survives a restart.
- Shared procedures. Skills and hooks in
.agro/serve every harness. - Opt-in access. SSH, the host Docker socket, Cloudflared tunnels, and Slack stay off until you turn them on.
How it works
- On the host, run
agro sandbox install docker. The sandbox runs the published image, so you need no project checkout. - Run
agro shell <name>, or attach VS Code. - In the sandbox, run
agro tool install herdrandherdrfirst — nothing installs at boot. - In a Herdr pane, install a harness, authenticate it, and start the agent.
The agent in the first Herdr pane at /home/sandbox/harness is the
orchestrator. The orchestrator manages git, the sandbox lifecycle, and the
shared agent setup. agro stop keeps the home volume. agro destroy deletes the
home volume, and it asks before it runs. See
Lifecycle commands.
For recurring work, use the native loop of your coding harness, for example
Claude Code /loop.
License
AGRO ships under Apache-2.0. Mifune's hosted control plane (the Mifune Console, provisioning, billing, and enterprise policy) is separate and proprietary.
Where to start
- Installation installs the
agroCLI. - Quickstart takes you to a working agent in the sandbox.
Report issues at github.com/mifunedev/agro.