Your setup stays put.
Files, installed tools, Docker images, and tmux history stay on your box between connections. No starting from scratch.
PERSISTENT DISK & STATEA HOME FOR YOUR CODING AGENTS
Your laptop can take a break. Your agents don’t have to.
Give Claude Code or Codex a persistent remote Linux box. Start the work, disconnect, and come back to the same session.
Open source. Full root access. Yours to run.
bh run work codex
Connected to box “work”
/opt/boxhaven/project
Refactor the settings page.
Reading project files…
Your agent runs here, on the box.
01 / A FAMILIAR WAY TO WORK
Keep your terminal. Keep your tools.
Give your work a place to stay.
Install the CLI, then sign in. Choose hosted BoxHaven or enter the URL of your own backend.
CLI installation guide ↗brew install finbarr/tap/boxhaven
bh loginHomebrew on macOS or Linux. More install options in the guide.
Run this in your project. BoxHaven creates a Linux VM named “work” and syncs your project once.
The box keeps its own files from here. Later changes sync only when you ask.
bh create workYour project arrives at /opt/boxhaven/project.
Start Codex in the box’s managed tmux session. Prefer Claude Code? Use bh run work claude.
Your existing agent account is used; agent and model charges are separate.
bh run work codexTo detach, press Ctrl-b, then d. The remote session keeps running.
Reconnect to the same box and tmux session. Your files, tools, and session history stay on the machine after you disconnect.
Destroy the box when you’re finished to stop compute charges.
bh connect workSame box. Same session. Pick up the thread.
02 / EVERYTHING IN ITS PLACE
Real machines for real projects.
Set up your environment and make it yours.
Files, installed tools, Docker images, and tmux history stay on your box between connections. No starting from scratch.
PERSISTENT DISK & STATEA full Linux VM with root access. Install what you need, use normal SSH, or open your box in VS Code Remote SSH.
bh ssh-config install
ssh bh-workPush local changes explicitly. Pull results back when you’re ready. Sync up mirrors deletions; sync down overwrites local files.
bh sync up work
bh sync down work --forceRoom for your whole workflow. Run agents on separate boxes, share access with your team, and share web apps through public preview URLs when configured.
Explore the docs ↗03 / PICK YOUR ADDRESS
Same open-source tools.
Two ways to feel at home.
We run the control plane and cloud infrastructure. You create a box and get to work.
Run the open-source backend with your own DigitalOcean or Hetzner credentials. Pay your provider directly.
A FEW GOOD QUESTIONS
Agents started in the remote box’s managed tmux session keep running. Your laptop can disconnect without ending that session. This doesn’t move an already running local process to the box.
Starting Claude or Codex forwards recent sessions for the current project. For Claude, use bh run work claude --continue to resume the conversation on the remote machine.
No. Creating a box syncs your project once. After that, use bh sync up work to mirror local changes to the box, or bh sync down work --force to retrieve remote work and overwrite local files.
No. Your box keeps running, so compute charges continue. Destroy the box when you’re finished to stop charges. See pricing for the hosted terms.
Good work deserves a place to keep going.
Make yourself at home ↗