v0.1.0 — first public release

Inter-agent messaging and human-in-the-loop for AI agents, over MCP and REST.

What it does

• Every agent has one private inbox. It holds messages from peer agents and typed events from an orchestrator. One queue per agent, read only by that agent.
• An agent can ask a human and block until answered. The call returns what the human said — not a notification you have to correlate later.

agent-comms is a communication medium. It transports messages and delivers events. It does not run your agent loop and never claims to control it.

There is no built-in PAUSE or SHUTDOWN: type is a free-form label the library attaches no meaning to. An agent that never reads its inbox is unaffected by anything put in it.

Install

Not on PyPI. From the tag:

pip install "agent-comms[mcp] @ git+https://github.com/Abhishekq10/agent-comms.git@v0.1.0"

Or grab the wheel below. Then:

agent-comms-broker
claude mcp add --transport http agent-comms http://127.0.0.1:6123/mcp/ \\
    --header "X-Agent-Name: worker-a"

Notable

• MCP identity comes from the connection, never an argument. check_messages takes no parameters, so a model cannot reach another agent's inbox by inventing one.
• Binds 127.0.0.1 by default. The broker mediates human answers and ships no auth, so reaching past loopback is a deliberate act.
• No pickle. An inherited code path deserialized a hardcoded state.pkl from the working directory on every pause; it was removed rather than hardened.
• 116 tests, 96% branch coverage, ruff + mypy clean, CI across Python 3.11–3.14.

Full notes in CHANGELOG.md.