agentbox-info

<!-- agentbox-managed:v1 --> # AgentBox (host-side) You are operating on the **user's host machine** (laptop / dev workstation), not inside a box. Use the `agentbox` CLI to provision isolated sandboxes for coding agents and to attach to them. If you find yourself *inside* a box (`/workspace` exists and `AGENTBOX_RELAY_URL` is set in the env), this is the wrong skill — use the in-box `/agentbox-setup` skill instead. ## What AgentBox is, in one paragraph AgentBox spins up one isolated sandbox per agent run — a local Docker container (default), a Hetzner VPS (`--provider hetzner`), a Vercel Sandbox (`--provider vercel`), or a Daytona cloud sandbox (`--provider daytona`, partial support). Each box has its own `/workspace`, but the host's `.git/` is shared, so commits made inside the box land on the host immediately. The agent inside the box has **no host credentials** — `git push`, opening URLs in the host browser, capturing checkpoints, and all other host-side operations flow through a small host process called the **relay** that runs alongside the CLI. ## The two starting commands ### `agentbox create` Provision a box and stop. The box exists and is ready, but nothing is launched inside it. ```sh agentbox create # docker, auto-named after the workspace agentbox create -n review # docker, friendly name agentbox create --provider hetzner # cloud VPS (requires `agentbox prepare --provider hetzner` once) agentbox create --attach ...