claude), Codex (codex), and OpenCode (opencode). Type the command from any directory and go. Forks and fresh machines have them too, since the agents are part of the image.
Claude Code starts already logged in on a fresh machine.
Already configured for boxd
Each machine carries an instructions file that every agent reads through its own convention:~/.claude/CLAUDE.md for Claude Code, ~/.codex/AGENTS.md for Codex, and ~/.config/opencode/AGENTS.md for OpenCode. It tells the agent about the environment: the in-machine boxd CLI, the default proxy, and how to create sibling machines, manage proxies, and clean up. You skip the part where you explain the platform, because the agent already knows it.
A repo-level CLAUDE.md or AGENTS.md merges on top, so your project conventions come for free as well.
The in-machine boxd CLI is pre-authenticated, so any of the three agents can create machines, exec into them, and expose ports without a token or key setup. See Machine to machine.
Logins
- Claude Code and Codex. Sign in once per organization, on any machine. boxd serves the login to every private machine you have in that org, new machines and forks included. The credential is stored encrypted, and you can disconnect it from the console.
- OpenCode. Run the
opencodelogin once on each machine. The login persists on that machine’s disk, and a new machine asks again.
ANTHROPIC_API_KEY (or the equivalent for the other agents) as an env var or secret and the same binaries use it.
Use them
Interactive:An agent that is always available
The machine keeps running when you disconnect, so an agent session that lives on the machine outlives your laptop. Three pieces make it permanent:tmux keeps the terminal session alive on the machine, Claude Code runs inside it, and remote control connects the session to your Claude account so you can drive it from anywhere.
A tmux session keeps the agent on the machine, and remote control makes it reachable from anywhere.
boxd connect myapp followed by tmux attach -t agent.
Many agents at once
One agent on one machine is the starting point. To fan a problem out across many agents in parallel, each on its own machine with a lead agent merging the results, see Agent swarm intelligence.FAQ
Do sessions survive a reboot?
Do sessions survive a reboot?
claude --resume <session-id>, and the same holds for the other agents’ session storage.Where do the Claude Code and Codex logins live?
Where do the Claude Code and Codex logins live?
Can the agents run Docker, systemd, anything?
Can the agents run Docker, systemd, anything?
Which instructions file wins when a repo has its own?
Which instructions file wins when a repo has its own?
CLAUDE.md or AGENTS.md merges on top of the boxd-provided one, so the agent keeps the platform context and adds your conventions.