BoxHaven

PERSISTENT REMOTE COMPUTE

Go offline.
Keep going.

Your laptop can call it a night.
Your agents don’t have to.

Give Claude Code, Codex, or your shell a persistent Linux box. Disconnect whenever. Come back to the same work.

Launch your first box See the flight plan

Open source. Full Linux. Your control.

BOXHAVEN / ORBITAL VIEWILLUSTRATIVE DEMO
Laptop offline. Remote session running.

A workflow illustration, not live box activity.

BUILT FOR THE LONG RUN Claude Code Codex Your shell SAME TOOLS. MORE RUNWAY.

01 / THE FLIGHT PLAN

Start here.
Pick up anywhere.

One named box. One persistent session.
A few commands between you and a longer run.

Read the quickstart
  1. 01

    Create your box

    Log in, then create a Linux box from your project directory. Your project syncs once.

    bh login
    bh create work
  2. 02

    Give it a mission

    Start Codex in the box’s managed tmux session. Claude Code works here, too.

    bh run work codex
    Your agent runs on the remote box.
  3. 03

    Go off the radar

    Press Ctrl-b, then d to detach. Close your laptop. The remote session keeps running.

    Ctrl+bthend
    Disconnected ≠ stopped.
  4. 04

    Return to your work

    Reattach to the same session. Your files, tools, and tmux history are still on the box.

    bh connect work
    Same box. Same context.
FIRST, INSTALL THE CLI
brew install finbarr/tap/boxhaven
macOS + Linux install options

02 / YOUR REMOTE WORKSPACE

A real machine.
Room to make
yourself at home.

Install your tools. Run Docker. Leave a task running. It’s a full Linux VM with root access, and it stays yours until you destroy it.

work / PROJECT MANIFEST
/opt/boxhaven/project
├── src/
├── tests/
├── .boxhavenignore
└── your-next-big-thing
FILES + TOOLS + SESSIONSTAY ON THE BOX ↗
A /

Sync on your terms.

Create syncs your project once. After that, the box owns its copy. Push local changes explicitly with bh sync up work; it mirrors deletions. Retrieve remote work with bh sync down work --force, which overwrites local files.

B /

Your SSH tools, right at home.

Run bh ssh-config install once, then connect with ssh bh-work. Use scp, rsync, or VS Code Remote SSH with managed, short-lived certificates.

C /

Bring your agent’s context.

Starting Claude or Codex forwards recent sessions for this project. Use bh run work claude --continue to resume a conversation on the remote box.

D /

Work worth sharing.

Give each agent its own box. Invite teammates with team roles, and share running web apps through public preview URLs when enabled on your backend.

03 / CHOOSE YOUR GROUND CONTROL

Your mission. Your infrastructure.

Explore the source
SELF-HOSTED

Your cloud. Your controls.

The same open-source backend, CLI, and VM runtime. Bring your DigitalOcean or Hetzner credentials.

Read self-hosting docs AGPL-3.0 / OPEN SOURCE
GOOD WORK DESERVES A PLACE TO KEEP GOING.