Conductor

Shared agent terminals. Launch coding agents such as Claude Code, Codex or Antigravity in real terminals, watch and drive them from the browser, and share a live session with other developers through a link. Inspired by webtty, rebuilt as a small server with a Nuxt UI workbench.

Two ways to run a session:

Both kinds show up in the same session list, use the same share links, the same terminal and the same in-browser file viewer.

Quick start

Requirements: Go 1.26+, Node 22+, and the agent CLIs you want to launch on the PATH of whichever machine runs them.

make deps                 # checks go/node/npm/python3, then go mod download + npm ci
make build                # generates the SPA and builds bin/conductor with it embedded
CONDUCTOR_WORKBENCH_TOKEN=change-me ./bin/conductor serve

Open , paste the workbench token when prompted, and press Launch agent. Without CONDUCTOR_WORKBENCH_TOKEN the server makes a random token at startup and keeps it in workbench-token in its data directory, mode 0600, while it runs: cat ~/.conductor/workbench-token (the default data directory) as the server’s user. The terminal and the log name the file, never the token. Every start without a token writes a new one there; a start with one configured removes the file. A second server started on the same data directory while the first runs cannot keep its own generated token there, so it stops unless a token is configured for it (or its parent reads --print-listen).

Host a session from your own machine instead:

CONDUCTOR_HOST_TOKEN=host-token ./bin/conductor host --server http://localhost:8080 -- claude

Your terminal is attached as a controller; the session appears in the UI as hosted. Add --relay-only to skip WebRTC entirely, --no-local to run it headless, or --stun stun:host:3478 to override the ICE servers. A server on another machine is https://: a plain http:// (or ws://) one that is not this machine (localhost in lower case, 127.0.0.0/8, ::1) is refused before anything is dialed, unless --insecure says to go ahead, and then the host says that what passes between it and the server (the session’s output, its viewers’ keys) travels in the clear and unverified. A redirect the server answers with is held to the same rule. The server is named by its