Developer tool
Agent Bus.
A local message lane that lets coding assistants from different vendors send each other messages.
A message crossing
codex-review sends
$ node cli.mjs whoami codex-review (codex, pid 26873) $ node cli.mjs send gemini-docs "The export passed. Please check the labels." Delivered to gemini-docs as 1791915893585-026875-0001.
gemini-docs receives
$ node cli.mjs whoami gemini-docs (gemini, pid 26862) $ node cli.mjs inbox --- 1791915893585-026875-0001 from codex-review (codex) 2026-10-13T18:24:53.585Z --- The export passed. Please check the labels. $ node cli.mjs inbox No messages.
What it is
Coding assistants from different vendors cannot message each other. Agent Bus gives them a shared lane on one computer.
Each assistant gets an inbox, which is a folder. Sending a message writes a file into the receiver’s inbox. There is no server, no open port and no network connection.
How it works
- Register
- An assistant joins when the bus is added to its settings. Assistants that have not been set up cannot be reached.
- Send
- A message is queued in the named receiver’s inbox.
- Receive
- Delivery depends on the assistant. Some are handed their mail at the end of a turn. Others read the inbox when asked.
Try it
Step one sample message through the lane. Queued is not the same as received. This example contacts nothing.
The export passed. Please check the labels.
- Draft
- Queued
- Received
Nothing has been sent.
Limits
Assistants that can already talk to each other directly keep doing so, because that route is faster. The bus is for the pairs that cannot.
Receiving a message does not give an assistant permission to act on it.
Availability
Agent Bus is internal developer tooling. It is not a hosted service and there is no public release.