Appearance
Quickstart
Connect to a box (nothing to install)
hopbox is live at box.hopbox.dev. Your SSH key is your identity — just connect:
sh
ssh proj@box.hopbox.dev # spawn/attach your box "proj", get a shell
ssh proj:debian-12@box.hopbox.dev # pick a catalog image
ssh images@box.hopbox.dev # list the image catalog (spawns no box)Reconnect with the same key and you get the same box back (within its lifetime). Files move like any SSH host:
sh
scp -r ./src proj@box.hopbox.dev:src # copy in
ssh proj@box.hopbox.dev "make test" # run a command (pipe-friendly, no pty)
rsync -az ./ proj@box.hopbox.dev:proj/ # sync a treeManage your boxes — ssh cli@host
No client to install; your key authenticates you:
sh
ssh cli@box.hopbox.dev ls # list your boxes
ssh cli@box.hopbox.dev rm proj # remove one
ssh cli@box.hopbox.dev # banner + your fleetSee ssh cli for all commands.
Hand a task to an AI
hopbox isn't just a place to log in — you can delegate. Store an agent credential once, then give a box a task and a coding agent does it in its own VM:
sh
# one-time: let your agent boxes use your Claude Code token
printf %s "$TOKEN" | ssh cli@box.hopbox.dev secret set CLAUDE_CODE_OAUTH_TOKEN
# delegate — the agent works, and asks you if it's unsure
ssh fixer:claude-code@box.hopbox.dev box-guest agent "add retry logic to api.py and run the tests"
ssh cli@box.hopbox.dev asks # questions your agents are blocked on
ssh cli@box.hopbox.dev answer <id> yesWatch it all — the fleet, agents working, their questions — in the web console at box.hopbox.dev/app. See Agent boxes.
Run your own server
One command on a Linux host with systemd (Docker backend, zero extra setup):
sh
curl -fsSL https://hopbox.dev/install.sh | sudo shPrivate beta
The repo is currently private, so the install one-liners need repo access (a token or a deploy key). Ask us for access — or just use the hosted box.hopbox.dev, which needs no install at all.
It installs hopboxd + hopbox-mcp + the in-box hopbox-agent + box-guest, writes a systemd unit, turns the AI-control MCP plane on by default, and starts on the docker backend. Then:
sh
ssh box@<your-host> # spawn a box on your serverFor the Firecracker microVM backend and TLS, see Deploy a server.
Next
- Boxes over SSH — images, lifetimes,
box-guest. - Agent boxes — delegate work to an AI; the
askloop. - The AI-control plane — let an AI drive the whole fleet.
- Deploy a server — the microVM host in detail.