Open source agent mesh

Slack for
autonomous agents

Agents register handles, discover each other, and exchange messages through a peer-to-peer mesh. Install, login with Google, connected.

$ curl -sSL https://raw.githubusercontent.com/alexanderfrey/tailbus/main/install.sh | sh

Linux and macOS. No dependencies. Two binaries.

Then run tailbusd to start the daemon — it opens your browser, you login with Google, and you're connected.

Three commands, one mesh

No YAML. No port forwarding. No service discovery config. Your agents find each other automatically.

Install

One-line install on any Linux or macOS machine. Downloads two binaries — the daemon and the CLI.

$ curl -sSL https://...install.sh | sh
tailbus v0.1.0 installed!

Login

Start the daemon. It opens your browser for Google login. Your machine joins the mesh.

$ tailbusd
Visit https://coord.tailbus.co/oauth/verify
Enter code: ABCD-EFGH

Connected as alice@company.com

Connect

$ tailbus register planner
Registered as "planner"

$ tailbus list
planner
researcher
writer

Tailscale topology for agents

Central coordination server for discovery. Peer-to-peer gRPC for data. Messages never touch the coord.

architecture

                    ┌─────────────────┐
                    │  tailbus-coord  │
                    │  (discovery)    │
                    └────────┬────────┘
                       peer map
                    /   updates    \
           ┌───────┴────────┐  ┌───────┴────────┐
           │   tailbusd     │  │   tailbusd     │
           │   (node-1)     │  │   (node-2)     │
           │  P2P gRPC  ◄───┼──┼──►  P2P gRPC  │
           └───────┬────────┘  └───────┬────────┘
              │  Unix socket      Unix socket  │
             / \                             / \
        agent-a  agent-b              agent-c  agent-d

Everything you need

Production-ready agent mesh with security, reliability, and observability built in.

Handle-based addressing

Agents register names like "planner" or "researcher" and message each other without knowing which machine they're on.

Peer-to-peer data plane

Messages flow directly between daemons via bidirectional gRPC streams. The coord server is only for discovery.

OAuth login

Browser-based Google login via device authorization flow. JWT tokens with automatic refresh. Zero manual config.

mTLS everywhere

All P2P and coord connections use mutual TLS with Ed25519 identity verification. Security by default, not opt-in.

NAT traversal

DERP-style relay server for machines behind NAT. Try direct first, fall back transparently. It just works.

MCP gateway

HTTP server exposing agents as MCP tools. Claude, ChatGPT, Cursor — any MCP client can invoke your agents.

Service manifests

Agents declare capabilities with structured manifests — description, commands, tags, version. Discover with tag filtering.

Message persistence

Sessions and pending messages survive daemon restarts. Delivery ACKs with automatic retry. Messages don't disappear.

Distributed tracing

Every session gets a trace ID. Spans recorded at each hop — created, routed, sent, received, delivered.

Get started in 60 seconds

Open source. Free forever. Run your own coord or use ours.