BoxHaven

A home for your coding agents

Close your laptop.
Keep the good
work going.

Give Claude Code, Codex, and your projects a cozy place to run. Persistent remote Linux boxes that keep working when you step away.

Hosted for you. Or at home on your own cloud.

A person leaves a sunny wooden workshop with their closed laptop while two friendly remote machines keep working at the bench.
work a little box, still at it.
Your agents, right at home Real Linux. Full root. Yours. Open source at heart

A small ritual. A lot of possibility.

Set it going.
Go live a little.

Your terminal is the front door. A few commands and your work has a place of its own.

  1. Make yourself a workspace.

    Log in, name your box, and create it from your project directory. BoxHaven provisions a Linux machine and syncs your project once.

  2. Leave something good running.

    Start Codex or Claude Code in the box’s managed tmux session. Press Ctrl-b, then d to detach. The remote session keeps running.

  3. Come back to your work.

    Reconnect with bh connect work. Your files, tools, and session history are right where you left them.

your little workshop

# from your project directory

bh login
bh create work

✓ box ready · project synced once

bh run work codex

↳ agent session running in tmux

# detach: Ctrl-b, then d

# reattach when you're ready

bh connect work
work is runningsession attached

Illustrative workflow. Your agent runs on the remote box.

Familiar tools. More breathing room.

A proper workspace.
Down to the details.

A green machine with a wrench, neatly arranged tools, and a potted plant on its workbench.

Real machines, room to make.

Full Linux VMs with root access on DigitalOcean or Hetzner. Install your tools, run Docker, and keep your environment between sessions.

Your usual way in.

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

A place for everything. You do the moving.

After the first sync, each copy is independent. Push local changes with bh sync up work (including deletions), or retrieve remote work with bh sync down work --force, which overwrites local files.

Take a look around the docs

Two ways to make yourself at home

Your haven.
Your way.

01 / HOSTED

We’ll keep the lights on.

We run the control plane and cloud account. You bring your project and your agent. A little less setup between you and your next idea.

Get a hosted box Explore usage-based pricing →
02 / SELF-HOSTED

Build on your own patch.

The same open-source backend, CLI, and VM runtime. Bring your DigitalOcean or Hetzner credentials and operate it in your own cloud.

Read self-hosting docs Open source under AGPL-3.0

Before you settle in

A few little
good-to-knows.

Does my local agent move to the box?

You start a new process on the remote machine. BoxHaven can forward recent Claude or Codex sessions for your project so you can resume the conversation. For Claude, use bh run work claude --continue. A running local process is not transferred.

Can I share what I’m building?

When previews are configured, your box has a public HTTPS URL for the web app you serve. You can also invite teammates and share boxes with owner, admin, and member roles.

What happens when I disconnect?

The box and its managed tmux session keep running. Reattach with bh connect work. Disconnecting does not stop compute charges; destroy the box when you’re finished. See pricing details.

Make room for your next idea.

Your little workshop is waiting.

Find your haven