dev-mux documentation

dev-mux gives you one always-on control plane — the hub — for driving AI coding agents (Claude Code and friends) across every machine you code on. You watch and steer live terminal sessions from a browser cockpit, your phone, or the terminal, and the sessions keep running on the hub even when your laptop sleeps or your network roams.

This is the docs-as-code site for the managed product at docs.dev-mux.com. Every page here is authored in the repo and published on merge, so the docs and the product ship together.

The three roles

dev-mux has exactly three roles. Knowing which one a machine plays tells you what to install.

• Hub — the always-on cloud control plane we manage for you. It holds the roster, the live cockpit, and the connection to every spoke. With the managed product you never build or operate a hub yourself; we provision it.
• Spoke — a code VM (or your laptop, a Raspberry Pi, a cloud box) that runs your agents. A spoke's only floor is bash, tmux, and git. You add spokes to your fleet.
• Device — anything you drive the fleet *from*: a browser, a phone, a terminal. A device runs nothing as a node; it just connects to your hub.

Where to go next

• Install dev-mux — get the tooling onto a spoke and connect a device to your hub.
• Set up Tailscale — the one pre-sales question, answered: generate a pre-authorized auth key and paste it into the onboarding wizard. This is the private network that lets your hub reach your spokes.
• Add spokes — register a new code VM (or Pi, or Mac) into your fleet.
• Updates — how managed hubs stay current, and how to keep spoke tooling fresh.
• Billing — plans, seats, annual pricing, and how Tailscale costs interact with the Team plan.
• Troubleshooting — the fixes for the problems people actually hit.

How connectivity works (the honest version)

Your hub reaches your spokes over a private Tailscale network. Session durability does not depend on any one client staying connected: the hub holds every session in tmux, and clients use tmux-backed sessions with automatic reconnect. Close your laptop, switch from Wi-Fi to cellular, come back an hour later — reconnect and you are exactly where you left off, because the work never lived on your client in the first place.

The Tailscale setup guide walks the whole connection story end to end.