You're running Claude Code across a dozen repos and five machines and losing the thread. dev-mux is the live cockpit over the whole fleet — every terminal, every agent, every box — in one place.
Fleet · repos
∞
terminals, never dropped
0
of your code on our servers
3
surfaces — web · iOS · glasses
∞
repos & machines you bring
The tab problem
Right now the answer lives in a dozen terminal tabs and SSH sessions you tab through by hand — and they drop the moment your Wi-Fi blinks. dev-mux turns the whole fleet into one screen you can actually read.
Hub & spokes
The hub is a robust, hyper-efficient, persistent coordinator. An intricate weave of mosh and tmux keeps every session alive across dropped connections, sleeps, and network switches — close your laptop on the train, reopen at your desk, and your agents are exactly where you left them. Each spoke is one of your repos, on a machine you control.
Persistent by design. mosh + tmux hold sessions through drops, sleeps, and IP changes — nothing to reconnect.
Bring your own compute. Spokes are your own machines — self-hosted, self-administered. The hub never runs your workloads.
Isolated by deployment. One hub per tenant — a hard boundary, not shared state.
You hold the keys. The hub relays terminals; it never custodies your secrets.
A spoke is any repo, on any machine you control
Surfaces
The same live fleet on the web today — and, soon, in your pocket and on your face.
web-app
payments-api
mobile-app
↳ api-gw
edge-cache
The full fleet in your browser — live terminals, presence, file trees.
Fleet
● 5Your whole fleet in your pocket — see who's waiting, jump into any terminal.
◢ payments-api needs input
“approve the migration” ▸ sent
Hands-free heads-up control. Glance at fleet status, voice a command, one-tap a session.
One cockpit
Real PTYs streamed over WebSocket → SSH → tmux. Open any agent's terminal from the web — and type back. Sessions persist through every network drop.
mosh + tmux keep every agent alive across drops, sleeps, and network switches.
A live map of devices, hub, and spokes — four-color status at a glance.
Tuned for Claude Code today; the SSH + tmux seam fits any terminal-driven agent.
Most AI dev tools pay for inference and execution on their servers. dev-mux pays for neither — agents run on your spokes, the hub only coordinates. Lower liability for you, structural margin for us.
Pricing
Every plan ships a dedicated hub sized for its fleet — with measured 10× headroom to spare.
For the indie power user.
Join waitlistFor small teams flying together.
Join waitlistFor orgs & the security-sensitive.
Talk to usNo. Your agents run on your own machines (spokes). The hub is a thin relay that brokers terminal access — it never executes your workloads or stores your code.
A spoke is one of your repos running an agent on a machine you control — a laptop, a cloud VM, a Raspberry Pi. You self-host and self-administer them; add spokes up to your plan's fleet cap and the hub keeps a live map of all of them.
No — that's the point. The hub uses an intricate combination of mosh and tmux to keep every session persistent across dropped connections, sleeps, and network changes. Close the lid, switch networks, come back hours later: your agents are right where you left them.
Today it's tuned for Claude Code, but the transport is agent-agnostic — it's SSH + tmux underneath, so any terminal-driven agent runner fits the same seam.
Each tenant gets an isolated hub (a hard boundary, not shared state). Hubs are private to your tailnet by default, you hold your own keys, and your spokes stay self-hosted and self-administered — your code and credentials never leave your perimeter.
Early access is rolling out to design partners now. Drop your email and we'll get you a hub.