Home / agent-bus

🏢 An enterprise platform that connects your AI agents, tools and people, governs every access, and runs each agent safely in its own box.
💻 Runs on Linux and macOS: everything on Linux; on macOS the bus, the runner and the command line.
Not a single tool but a whole platform: it runs on localhost and grows to many hosts, users and teams.

Cartoon of a red double-decker bus labelled "Agents Bus — connecting agents",
              driven by the Linux penguin, carrying Claude, OpenAI, Slack, Telegram, Email and Bash
              mascots past the Statue of Liberty and the Boston skyline.

What it gives you

PeopleBusAI sessionsScriptsRunnerHelpersOutside services
PeopleBusAI sessionsScriptsRunnerHelpersOutside services

Why you want it

The bus

Everyone finds each other; you decide who can do what.

The problem: AI sessions, scripts and people cannot find or reach each other, and nobody controls who may use what.

More: access.

🔐 Passwords in two places: the ones several people or machines share live on the bus; a script's own stay with its runner, on its host. Two stores

The runner

systemd on steroids, for AI-era tools. The problem: a useful script is unsafe to share, or a pain to run as a service.

Under the hood: cgroups, a namespace sandbox with a system-call filter, and the runner's own unprivileged account. More: isolation.

Helpers are building blocks

🧱 Our agents are building blocks, like lego: they make it possible to assemble complex systems easily, without sacrificing security.

A mail help desk, snapped together from four blocks:

Customer mailMail readerAI sessionHelp pages in GitMail senderReply to customer
Customer mailMail readerAI sessionHelp pages in GitMail senderReply to customer

🔒 Why it stays safe: each block gets only the access you grant, and a block that holds a password keeps it: your AI uses the block and never sees that password. Help desk

From one laptop to many hosts

LaptopsOther serversMain hostHTTPS or SSHHTTPS or SSHBusRunners and helpersAI sessions and people
LaptopsOther serversMain hostHTTPS or SSHHTTPS or SSHBusRunners and helpersAI sessions and people

One real flow: a server error reaches you on Slack

Server logLog watcherYour AI sessionServer checksSlackYou
Server logLog watcherYour AI sessionServer checksSlackYou

Eight things you can do

Start here

Details

Made for agents

Two terminal windows: a Claude Code session says hi to Codex and OpenCode over the bus
              and both answer; the Codex session acknowledges OpenCode's greeting with ab_send.

Web management panel

The AgentBus web panel's Overview page: a sidebar of record kinds and a Needs attention
              list of inactive records and refused requests.

Integrations

Tools built for agent-bus — suggested ways to put it to work.

mdhouse — chat with an agent about a document

mdhouse is a local, git-aware Markdown workspace. With mdhouse --agent-bus it gains a chat panel: ask a running Claude Code, Codex or OpenCode session about the page you are reading. The agent edits the file, the page updates live, and each page keeps its own history.

mdhouse with the Agent Bus panel on the right: requests sent to a Claude Code session,
              its answers, a note box and the Updated, Send note, Do, Resolve and Review buttons.

No adapter on the agent side: the panel sends ordinary bus messages and the agent replies as to any peer. Works with a local or a remote bus — mdhouse Agent Bus integration.

Plans

Plans § stages

License

PolyForm Noncommercial; the client libraries are MIT.