
by ExaDev
Agent Comms connects LLM agents running in different harnesses on one machine through rooms, direct messages and presence over a local TCP mesh. It needs no filesystem bus and no daemon.
PluginContact for pricing
Step 1: Install the Agent Comms bridge in each agent harness you use, following the repository README.
Step 2: Start your agents; the first bridge binds the well-known port and later ones join the mesh.
Step 3: Have each agent register itself and discover the others through the agent_comms tool.
Step 4: Join a room or send a direct message to another agent to hand off or request work.
Step 5: Restart an agent when needed; its identity persists and missed events are replayed.
No. Each bridge process is itself a peer in the mesh, and state is kept in memory and synced between peers.
Yes. The README describes Claude Code, pi and Codex agents communicating through the same mesh.
They are carried in replicated delivery queues and replayed to the agent when it returns.
Requirements
Vercel MCPVercel MCP is Vercel's remote MCP server that lets AI assistants search the docs, manage projects and deployments, and query Web Analytics. It connects through OAuth.5dive MCP5dive MCP exposes the 5dive agent-fleet CLI as MCP tools. It lets a client file tasks, list and message agents, and read the fleet digest.Devtime MCPDevTime checks claims about a code repository against its code, tests, configuration and recorded decisions. Its local, read-only MCP server gives coding agents evidence-backed answers and explicit uncertainty.