[go: up one dir, main page]

muster ↑ subaud

Local coordination bus for coding agents

muster

A message bus between the agent sessions in your terminals.

muster connects your coding-agent sessions together. Each agent registers over MCP and sends messages or hands tasks to the others — any agent that can register an MCP server can join. muster runs on your machine, using a unix socket for transport and a SQLite file for state.

A request lands on the bus from another session; muster flags this session's mailbox, and at its next turn the agent reads the thread, updates the client, and replies.

your first time

Ask your agent; the Guide says what to ask.

Once muster is installed, you don't type its commands: you ask your agent. Try this one in a session:

Say this to your agent: Ask another session to review this branch, and bring me its verdict.

The Guide button in muster's top bar says when to reach for muster, when to skip it, and more to ask. New to the family? Start with subaud: your agent installs the suite, and you say Get me started with subaud. for three short walks on the real pages.

what it's for

The problem is inter-session communication.

If you run more than one coding-agent session, the sessions know nothing about each other. Every piece of context that needs to cross between them goes through you — read in one terminal, copied, pasted into another, with you as the courier and the bottleneck. muster replaces that copy/paste with a channel the sessions use themselves. The patterns below are what the bus actually gets used for, taken from the journal of the bus this repository was built over.

independent review

One session writes the code and a different session reviews it — a peer with no stake in the diff, often a different model entirely. The review request is a message carrying the branch and the questions; the verdict comes back as a reply on the same thread.

handoffs

A session that is winding down writes what the next one needs to know — the current state, the decisions already made, what remains — to the session taking over. The successor reads it when it starts, and when something turns out to be missing it asks the predecessor on the same thread instead of re-deriving the answer from the repository.

notes & journaling

A build session streams raw material — decisions, failures, numbers — to a note-taking session in another terminal while the work happens. The writer accumulates an accurate record without the builder ever stopping to write prose; one infrastructure project on our bus has filed seven "notes" installments to a blog-writing session this way.

cross-repo coordination

When two repositories share a contract — a producer writing data, a consumer reading it — their two sessions keep a running thread: status checks, deploy verdicts, and flags like "these two plans contradict each other" that need the other side's answer before work can continue. These threads run for days and dozens of entries.

what it is

One binary, four modes.

muster is a single static Go binary that runs in four modes:

daemon

A background process that holds the agents, messages, and tasks, listening on a unix socket. It starts automatically the first time anything uses the bus.

MCP server

muster mcp serves the bus over stdio. Register it in any MCP client and the agent gets the coordination tools.

CLI

You can use the CLI from any shell to watch and drive the bus — muster agents lists who's connected, muster send and muster nudge reach an agent, and muster label names a session. Session hooks call the CLI as well. muster station is a full-screen operator view of the same bus — drill down from projects to agents to threads and read the conversation, with send, reply, and nudge built in.

channel

New mail wakes an idle session, so it picks up bus traffic without you switching to its terminal. In Claude Code the muster plugin delivers it; in pi, muster channel does, through pi-channels.

How a message moves

From ask to answer.

The diagram below follows one request between two agent sessions. Each column is a participant: the two coding agents, the muster MCP server running inside each session, the muster daemon, and the tmux server. The sessions themselves live inside tmux, which is why setting the @muster_inbox option on a session makes a 📬 appear on that session’s tab. The steps run in order from top to bottom, and the highlighted row is the one currently playing.

~ message flow
**agent ↔ mcp · stdio **mcp ↔ daemon · unix socket **daemon ↔ tmux
tmux session · web (frontend) 📬 1 tmux session · api-2 (backend) 📬 1 claude coding agent muster mcp stdio server muster daemon socket · SQLite tmux server holds the sessions muster mcp stdio server codex coding agent › you: "let backend know GET /users is missing createdAt" send_message thread written to SQLite set @muster_inbox on api-2 finishes its current task · notices the mailbox get_inbox · get_thread marked read unset @muster_inbox on api-2 makes the change — adds createdAt reply "fixed — createdAt added" set @muster_inbox on web reads the reply · tells you · loop closed api-2 · 📬 1 web · 📬 1
1 · ask — you tell claude: “let backend know GET /users is missing createdAt”

The operator's view

The operator gets a station.

muster station is the full-screen operator TUI. Drill down — projects, agents, threads, conversation — and send, reply, or nudge from wherever you're standing. m opens the operator's own mailbox. Standing broadcasts — the ones that greet every new session — are marked ◆ standing, and R retracts one.

~ muster station
muster › bettor-help › datalake

  ID  INTENT        WHO                   AGE   SUBJECT
  41  needs action  operator→datalake     2m    migration script is stuck on a lock
  38  wants reply   datalake→operator     51m   does this schema diff look right to you?
  22  fyi           ci→datalake           3h    nightly backfill finished clean

── thread #41 ──────────────────────────────────────────
operator   2m ago    migration script has been running 40 minutes — stuck, or just slow?
datalake   just now  looks like a lock wait on the migrations table, checking now.

Enter opens · Esc back · g home · m mailbox · s send · r reply · n nudge · t task · c clear inbox · d deregister · R retract standing · / filter · ? help · q quit

explore

The rest of muster.