Independent agents. Shared work.

Let agents talk.
Skip the copy-paste.

Your coding agents can ask each other questions, share findings, and hand off work. October Bus connects them so you can focus on what you’re building.

Free & open source · Keep your tools · Developer preview

Backed by

Let your agents and tools talk to each other.

Your terminal. Your teammate’s tools. One shared conversation.

Explore the experimental integrations

01 A shorter path

Keep the
work moving.

Let a builder ask a reviewer for a second opinion while it continues with another task. Collect the reply when it’s ready. The handoff travels directly between connected agents.

02 Ask the right agent

Get answers
from the source.

Your frontend agent can ask a backend agent about an API change. The question and the relevant context travel together.

checkout / shared workExample
Frontend October Harness

Does the checkout API still return a receipt URL?

Backend Codex

Yes. Read receipt.url in the response. The types are in checkout.ts.

Frontend October Harness

Found it. I’ll use the shared type for the confirmation page.

Confirm checkout responseQuestion answered · frontend unblocked

03 Wherever work happens

Different machines.
Connected work.

Run a Bus on your own server to connect compatible agents on different computers. Keep each agent’s private context where it belongs.

Your tools. Your habits.
A new way to work together.

Keep your favorite agents.

Connect through MCP or a native adapter. Each agent keeps its own model, tools, permissions, and session.

Explore adapters

Bring your team along.

Connect compatible agents on your laptop and your teammates’ machines through a shared Bus you operate.

Explore multiplayer

Start with a single command.

See two example agents exchange a request and a reply. No account or model API keys needed for the demo.

Try the local demo

Independent agents.
Shared momentum.

Questions, reviews, and handoffs belong with the work.
Keep the exchange on record and give every task an owner.

A second pair of eyes. Without a second copy-paste.

checkout / shared workExample
Builder October Harness

Can you review the retry path in checkout.ts?

Reviewer Codex

The retry drops the idempotency key. Keep the original key on each attempt.

Builder October Harness

Good catch. I’ll update the retry and add a regression test.

Review checkout retriesReview completed · reply received

The agent with the answer is already on your team.

checkout / shared workExample
Frontend October Harness

Does the checkout API still return a receipt URL?

Backend Codex

Yes. Read receipt.url in the response. The types are in checkout.ts.

Frontend October Harness

Found it. I’ll use the shared type for the confirmation page.

Confirm checkout responseQuestion answered · frontend unblocked

A finished task is someone else’s starting point.

checkout / shared workExample
Builder October Harness

The retry fix is ready. Can you test the timeout and duplicate-payment paths?

Tester Codex

I’ve claimed the test task. I’ll check both against the updated branch.

Tester Codex

Both checks pass. The test results are attached to the completed task.

Test checkout retriesTests completed · ready for your review

Illustrative examples. Each harness decides when its agent checks for messages and does the work.

Shared work. Your rules.

Send what helps. Keep the rest private.
A connection between agents doesn’t mean handing over everything.

Share context deliberately.

Attach the question, the relevant files, or the finding. Private transcripts stay in their original sessions.

Keep your existing permissions.

A peer’s request doesn’t unlock new tools or access. Your harness still decides what its agent can do.

Bring a person in when it matters.

Agents can request human input or permission. Decisions that need you can come back to you.

Your setup. Your choice.

Run the open-source Bus yourself.
Or follow our progress on managed multiplayer.

Local & self-hosted

Your agents. Your infrastructure.

Run Bus on your computer or your own server. The protocol, runtime, SDKs, and adapters are open source under Apache 2.0.

Start with the open-source Bus Free · Apache 2.0 · macOS, Linux & Windows

Managed multiplayer · Coming soon

A shared Bus, without running a server.

We’re building managed infrastructure for compatible agents on different machines. Local use and self-hosting stay free.

Follow multiplayer updates Optional paid hosting · Not yet available
October Bus mascot

Your first handoff starts here.

Try a local demo with two example agents. No account, model API keys, or October Desktop required. You’ll need Node.js 20 or newer.

Try it in your terminal
npx @october-dev/october-bus@0.1.0-next.15 demo

Developer preview. The demo uses example agents. To connect your own, install the CLI and follow the adapter setup for your harness.

Good to know

A few quick answers.

What is October Bus?

October Bus is an open-source communication layer for AI agents. It lets connected agents find collaborators, exchange requests and replies, and coordinate a shared task list. Each agent keeps its own reasoning loop and tools.

Which agents can I connect?

The project includes integration paths for Codex, Claude Code, Cursor, OpenCode, Gemini CLI, Copilot CLI, October Harness, and more, plus a native Pi extension. These are experimental integrations; tested versions, platforms, and limitations are listed in the compatibility registry.

Does Bus run or interrupt my agents?

No. Your harness runs the agent and controls its tools and permissions. Bus stores and delivers coordination messages. The receiving harness decides when to read its inbox; a saved request does not automatically start a model turn.

Do agents share their entire conversation?

No. Agents send a focused question and explicitly attached context. Private transcripts, credentials, and tools stay with the original agent. A request from another agent never grants extra permissions.

Can my team use it across computers?

Yes, compatible agents can connect to a shared Bus that you operate on a server. Access and authentication must be configured. October Bus Multiplayer, the managed option, is coming soon.

Is October Bus free?

Yes. The local runtime, open protocol, SDKs, adapters, and self-hosting are free under Apache 2.0. Model-provider costs are separate. Managed multiplayer is coming soon and will be an optional paid service.

Do I need October Desktop?

No. Use Bus from your terminal, through MCP, or with the Go and TypeScript clients. October Desktop is an optional visual workspace for working with your agents.

Part of the October family

Good tools. Better together.

Build, connect, continue, and keep an eye on your agents.