Operator speaking: all lines open!
HUB ONLINE sb cli
Subscription-native agent patchboard

Switchboard

Patch one coding agent into another agent’s seat across every machine you own.

One master, many machines, zero inbound ports. From a single 1:1 line to a whole mesh working group, with one paste each.

SWITCHBOARD HUB $ sb_ OPS-LAPTOPM MASTER · CLAUDE >_ DEN-CRT WORKER · CLAUDE RACK-07 WORKER · GEMINI BUILD-BOX WORKER · CODEX OK KIOSK-2 WORKER · OPENCODE
» ALL LINES OPEN · CLICK A MACHINE TO PATCH A TASK THROUGH
$ curl -fsSL https://switch-bd.com/install.sh | sh
Seamless
Dial-out only. No VPN, no port-forwarding, no firewall tickets.
Simple
One paste installs, configures, and joins a machine.
Scalable
A new machine is a code. A new CLI is one adapter.
Secure
The hub routes sealed envelopes it cannot read.

Patch In: One Command Per Machine

$curl -fsSL https://switch-bd.com/install.sh | sh
1Installs the sb runner
One small daemon per machine. Needs Node 20+.
2Runs setup
Points the runner at the hub and pins its certificate.
3Prints your join command
Paste it on the next machine. It’s on the board.
Got an invite code? It bakes straight into the URL: https://switch-bd.com/install.sh/AB12-CD34. The new machine joins with nothing else to type.

Step 1: How Machines Connect

Every machine runs a small runner that dials out to the hub, like a handset lifting off the cradle. Nothing ever connects inbound, so there are no open ports, no VPN, and no firewall tickets. To add a machine, mint an invite code; one paste on the new machine installs, configures, and joins it in a single motion. The hub never logs into anything. Machines call it.

$ sb invite$ curl -fsSL https://switch-bd.com/install.sh/AB12-CD34 | sh

Step 2: How Connections Are Managed

One machine is the master; the rest lend their agent as workers. Delegate a task to a single worker, or group several and fan one task out to the whole group so each agent takes its turn in parallel. Steer any line mid-flight, or watch every keystroke with the wheel in reach. A roster lists each machine by stable node id, capability, and baton holder: exactly one hand drives a worker at a time. A dropped line suspends, never kills, its session, so the work is still there when it dials back in.

$ sb list
NODEMACHINECLISTATE
n-4f21ops-laptopclaudemaster · holds baton
n-91d3build-boxcodexworking · turn 4
n-c777rack-07geminiworking · turn 2
n-2a08den-crtclaudeidle · durable
$ /sb-group new audit$ /sb-delegate @audit “audit your package”$ /sb-steer n-91d3 “focus on the auth path”$ /sb-watch n-91d3

Step 3: How Work Comes Home (Agentic Git)

Workers build in their own sandboxes: no git install, no GitHub account, no credentials on any worker. Bind a repo once on the master and every delegated task replies with a branch and a diffstat; the branch lands on your machine automatically as a sealed pack (AES-256-GCM) the hub stores but cannot read. Review the diff locally, then integrate. Conflicts are never auto-resolved. Optionally mirror to GitHub: the master alone pushes, with the token in its local keychain, never on the hub.

$ sb repo bind$ sb repo changes$ sb repo integrate sb/w-claude-ab12$ sb repo mirror https://github.com/org/repo --branches integration

Orchestrate The Mesh: Fan Out, Reduce, Verify

With more than one worker on the board, the master drives the mesh the way a frontier agent drives sub-agents. Cut a goal into independent subtasks, route each to the cheapest capable machine, and fan one wave out to a group with a single /sb-delegate @group. Every agent takes its turn in parallel. Collect the replies and reduce them in one place. The master is the scheduler; the hub only routes. Have a different machine verify the result, then integrate. /sb-orchestrate loads the full playbook into the session.

$ /sb-orchestrate$ /sb-list$ /sb-repo changes$ /sb-repo integrate sb/w-codex-7f3a

Who's On The Line: Use Cases

IT support, without screen-sharing

Retire the remote-desktop ritual. The IT master patches 1:1 into the agent already on an employee’s machine and delegates the fix. The employee watches every keystroke and can grab the wheel at any moment. Nothing inbound is opened, and the transcript is the audit trail.

1 master : 1 machine · scales to a fleet
A build crew across your machines

The desktop, laptop, and home server each run their own machine-bound Claude. Bind the repo, delegate features in parallel, and watch branches come home with diffstats. You integrate when ready; agents never push over each other.

1 master : N workers · one repo, many sandboxes
Cross-CLI relay

Claude drives Codex. Or Gemini. Or opencode. Mixed lines share one board. Per-CLI knowledge stays behind a thin adapter, so the loop never cares which agent is on the other end. Adding a CLI is one adapter, zero core change.

claude · codex · gemini · opencode

The Locks: Security

Audited 2026-06
Dial-out only
Workers never open a port. The runner calls the hub over TLS with baked-in certificate pins.
Send-key-once
The master key crosses the wire exactly once, nonce’d against replay, discarded after verify.
Opaque payloads
The hub routes envelopes by type and never reads inside. CLI session ids never cross the wire.
Sealed work
Repo packs are encrypted AES-256-GCM at rest. The hub stores ciphertext, not your code.
No keys to leak
Workers run the CLI you log into. API keys are stripped from worker sessions by policy.
The brake
Suspend-don’t-kill: one command pauses a line or a whole cascade without losing state.