A HOME FOR YOUR CODING AGENTS

Clock out.
Code on.

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.

THE REMOTE DESKTOP, REIMAGINED
work — agent session
Linux / tmux● RUNNING

bh run work codex

Connected to box “work”
/opt/boxhaven/project

Codex

Refactor the settings page.

Reading project files…

Your agent runs here, on the box.

work: 1 sessionpersistent by design
Your laptop: connected
work.box
A smiling pixel box
Still here.
Still working.
● BOX ONLINE
INTERACTIVE WORKFLOW ILLUSTRATION

Real Linux machines Persistent agent sessions Direct SSH access Hosted or self-hosted

01 / A FAMILIAR WAY TO WORK

A few commands.
A whole other computer.

Keep your terminal. Keep your tools.
Give your work a place to stay.

Getting startedRead the manual ↗
STEP 01 / 04

Make yourself at home.

Install the CLI, then sign in. Choose hosted BoxHaven or enter the URL of your own backend.

CLI installation guide ↗
ON YOUR LAPTOP
brew install finbarr/tap/boxhaven
bh login

Homebrew on macOS or Linux. More install options in the guide.

STEP 02 / 04

A box with your name on it.

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.

FROM YOUR PROJECT DIRECTORY
bh create work

Your project arrives at /opt/boxhaven/project.

STEP 03 / 04

Let your agent settle in.

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.

START ON THE REMOTE BOX
bh run work codex

To detach, press Ctrl-b, then d. The remote session keeps running.

STEP 04 / 04

Right where you left it.

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.

WELCOME BACK
bh connect work

Same box. Same session. Pick up the thread.

Your laptop is the connection. The box is the workspace.

02 / EVERYTHING IN ITS PLACE

A proper computer.
With a good memory.

Real machines for real projects.
Set up your environment and make it yours.

FILE / 001

Your setup stays put.

Files, installed tools, Docker images, and tmux history stay on your box between connections. No starting from scratch.

PERSISTENT DISK & STATE
FILE / 002

Take the keys.

A 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-work
FILE / 003

Sync on your terms.

Push 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 --force

Room 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

Our cloud. Or your cloud.

Same open-source tools.
Two ways to feel at home.

BOXHAVEN SELF-HOSTED

Your infrastructure.
Your call.

Run the open-source backend with your own DigitalOcean or Hetzner credentials. Pay your provider directly.

A FEW GOOD QUESTIONS

Before you
close the lid.

What keeps running when I disconnect?

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.

Can I continue a local agent conversation?

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.

Are my local and remote files always in sync?

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.

Does disconnecting stop billing?

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 ↗