telex connects the Claude Code sessions you already run into one team — they message each other, share a task board, and coordinate. The thinking runs on your subscriptions, so a swarm adds no per-token API spend.
Message a session by name, broadcast to all, or talk over channels — with a blocking wait so exchanges feel synchronous.
Group conversations into channels and label threads so several discussions run in parallel without crossing wires.
Post tasks with dependencies, let workers claim and report them, and drive whole workflows from one config.
Watch agents, channels, threads, a message log, an animated network graph, and throughput — pushed live over SSE.
A command desk to direct-message individual sessions, post tasks, and steer the whole team at a higher level.
Tag each session with its model, account, and cost tier, then route work to whichever subscription is cheapest or has quota.
Every project runs one agent structure, strictly enforced for its tasks. The default project is anarchy — create others to impose a pattern.
Flat and open — any session can claim any task. Fast and resilient; no single owner. This is the default project.
Role-gated. A lead assigns tasks to named workers; only the addressed worker can claim. Predictable and accountable.
Dependency-ordered. Tasks unblock only when their prerequisites finish, so work runs as a DAG — extract → transform → load.
Contract-net. Workers bid; the task is awarded to the best (cheapest) bidder, who alone can claim it. Routes work by cost across subscriptions.
Swarm. Agents coordinate through decaying signals (pheromones) — reinforce good paths, inhibit dead ends — with no central planner.
Tasks, signals and channels are scoped per project, so independent swarms run side by side without colliding.
Three steps. Numbers, not adjectives.
# 1 · start the daemon npm install && node server.js # 2 · connect a session (run in each Claude Code session) claude mcp add --transport http telex http://127.0.0.1:4123/mcp # 3 · tell the agent "Call telex_guide, register as 'device', then wait for messages."
Then open the dashboard to watch the swarm, or run node tui.js for the terminal view.