BoxHaven. A home for
work in progress.
Get a box
Persistent remote Linux boxesBuilt for the work ahead / 01

Close the
laptop.
Keep going.

Give Claude Code, Codex, and your next big idea a place to keep working. Real Linux boxes. Persistent sessions. Ready when you return.

Start on BoxHaven See how it works
Fig. 01Presence ≠ progress
A disconnected laptop and a remote Linux box. Inside the box, the agent, files, and tmux session persist independently of the laptop connection.
You disconnect.
The box keeps running.
Open source. Yours to run.Claude Code / Codex / Your shellScroll to explore
01 /The workflow

A short setup.
A longer runway.

Start an agent on a named box. Leave it working in its own tmux session. Come back to the same files, tools, and history.

  1. 01

    Give your project a home.

    Log in, then create a box from your project directory. BoxHaven provisions the machine and syncs your project once.

  2. 02

    Put your agent to work.

    Start Codex or Claude Code on the box, inside its managed tmux session. It runs on the remote machine.

  3. 03

    Step away. Pick it back up.

    Press Ctrl-b, then d to detach. Reconnect whenever you’re ready. Your session stays on the box.

Quickstart / from your project
# 01 — Log in and sync your project once
bh login
bh create work

# 02 — Start Codex on the box
bh run work codex

# 03 — Ctrl-b, then d to detach
# Come back to the same session
bh connect work
Your session lives here. Not on your laptop.

New here? Install the bh CLI first Already use Claude? Run bh run work claude.

02 / The principleIndependent by design

Your connection ends.
Your work doesn’t.

A box is a full Linux machine with root access. Your files, installed tools, and agent session stay there when you disconnect. The laptop is how you get in. The box is where the work happens.

Meet your dev box
03 /The working details

Remote machine.
Familiar tools.

Keep the tools you know. Get a workspace that doesn’t depend on an open laptop.

a.

SSH, as it should be.

Use your terminal, scp, rsync, or VS Code Remote SSH. Set up managed aliases once; connections use short-lived certificates.

bh ssh-config install
ssh bh-work
b.

Your files. Your call.

The box owns its copy after creation. Push local changes explicitly, or pull the box’s work back. Sync up mirrors deletions; sync down overwrites local files.

bh sync up work
bh sync down work --force
c.

Pick up the conversation.

BoxHaven forwards recent local Claude and Codex sessions when you start those agents. Resume your Claude conversation on the box.

bh run work claude --continue
d.

Make room for the team.

Share boxes with owner, admin, and member roles. On hosted BoxHaven, share a running web app with its public preview URL.

Explore the documentation
04 /Your infrastructure

Two ways in.
The same freedom.

One open-source project. Choose who runs the control plane.

05 /Before you go

A few good questions.

Does closing my laptop stop the box?

No. The agent runs in the remote box’s managed tmux session. Detach with Ctrl-b, then d, and reconnect with bh connect work. Destroy the box when you are finished to stop compute charges.

Are my local files continuously synced?

No. Creating a box syncs your current project once. After that, bh run leaves the box’s files alone. Use bh sync up work to push local changes, including deletions, or bh sync down work --force to retrieve remote work and overwrite local files.

Can I use my existing agent account?

Yes. BoxHaven forwards selected local agent login files and recent Claude or Codex sessions for the project. Agent subscriptions and model API charges are separate from BoxHaven compute pricing.

Can I run BoxHaven on my own infrastructure?

Yes. The backend is open source under AGPL-3.0. Use your own DigitalOcean or Hetzner account, and operate the control plane yourself. Read the self-hosting guide.

Make yourself at home.

Leave something
running.

Create your first box