Fleet Bus — AI skill for Claude Code

Fleet Bus

**A tiny, file-based message bus that lets AI coding agents talk to each other on one machine.**

Run Claude Code in one window, Codex CLI in another, and a Grok bot or your own script in a third. With Fleet Bus they can hand each other tasks, report results, broadcast rules, and wake each other up. There is no server, no daemon, no database, no MCP server and no account. It is one Node.js file with zero dependencies, plus a folder of JSON files.

Any agent that can **run a shell command** and **read its output** can join, whichever vendor or model it comes from.

 ┌──────────────┐   send --to builder-a    ┌──────────────┐
 │ Claude Code  │ ───────────────────────▶ │  Codex CLI   │
 │ (lane: main) │                          │ (lane: bldr) │
 │              │ ◀─────────────────────── │              │
 └──────────────┘   send --to main         └──────────────┘
        │   ▲             (report)                 │
        ▼   │                                      ▼
   ~/.claude/fleet/main/inbox/*.json      ~/.claude/fleet/builder-a/inbox/*.json

---

Why

Once you run several AI coding sessions in parallel, for example one per git worktree or one per task, they need to coordinate:

• An orchestrator session hands a bounded task to a builder session and gets a report back.
• A rule changes (a new branch policy, a new model to use), and every running session needs to hear it once.
• A session finishes a milestone (a PR merged, a deploy done), and the others must rebase or react.
• A session is waiting on another one and should wake up when the answer lands, instead of polling in chat.

Chat-level "send a message to the other conversation" features only work inside one app, and usually only while the target is open. Fleet Bus is vendor-neutral and durable. Messages sit on disk until the receiving lane reads them, even when it is closed.

How it works

Lanes

A **lane** is a mailbox that one agent session owns. By default a lane's