Documentation
Berth documentation
Run coding agents on your own dev boxes, and work with them as if they were on your laptop.
Berth connects a laptop to any number of development machines (a VPS, a cloud VM, a desktop under your desk) and gives each repository on them worktrees, terminals, agents, dev servers and automations. The agents run on the boxes, so closing the app, sleeping the laptop or losing Wi-Fi never stops them; the app is a view you can close and reopen at any time.
Install on a box
curl -fsSL https://berthd.app/install | shIt installs berthd, starts it and prints a pairing link. On your laptop,
build the app and the berth CLI from source (there are no packaged builds
yet), then paste the link into the app or run berth pair '<link>'. Every
step is in install.
Start here
Install
One line on a box; the app and CLI from source on your laptop.
Add a box
Pair with the link a box prints, or install over SSH.
First project and worktree
Register a repository and branch off it.
First agent
Start Claude Code or Codex in a worktree and watch it work.
What it does
- Workspaces per worktree. Terminals, splits, and browser tabs onto each
worktree's dev server, at private URLs like
http://billing.cal.devl.localhost:1377/. - Agents you can see and steer. Claude Code, Codex and others, with a dashboard of who needs you, a review inbox for finished work, and orchestration (prompt, wait, check, loop, hand off) from the app, the CLI, or other agents.
- Projects set up the same everywhere. Each worktree gets its own ports,
environment, services, hooks and flows, from the repository's
.berth/config.json, a shareable kit, or the box's own config. - Automations. Flows on events, schedules or GitHub activity, running on the box; plus plain shell hooks and gates.
- Plugins. React plugins for the app, with built-ins for git changes, pull requests, dev servers, box monitoring, activity and notes.
- Boxes without the fuss. Pinned mutual TLS, pairing by link, boxes on other tailnets, self-upgrade over Berth's own connection, and a phone companion served by each box.
The pieces
| Piece | What it is |
|---|---|
berthd | The daemon on each box: worktrees, sessions (tmux), services, hooks, flows, kits. |
berth | The laptop CLI and background agent: connections, private URLs, the app's API. |
app/ | The desktop app (Tauri, React, coss ui). |
plugins/ | Built-in plugins, written against packages/plugin-sdk. |
kits/ | Kits, such as cal-com. |
Read how Berth works for the whole picture, or the security model before you pair a box you care about.