Proposal: Agent Message Bus (A2A plugin) for official Hermes integration

[kriszmac4]

Proposal: Integrate Agent Message Bus as an official Hermes A2A plugin

Repo: https://github.com/kriszmac4/a2a-communication-protocol
License: MIT, Python 3.10+, stdlib-only
Release: v1.0.0

What is it?

The Agent Message Bus (AMB) is a pull-based agent-to-agent communication protocol for Hermes. It enables async messaging between different Hermes profiles using SQLite, MCP tools, and cron.

Key features

• SQLite message persistence + idempotency + correlation tracing
• MCP tools (send_bus_message, agent_read_messages, agent_discover)
• Cron layer for autonomous routing, watchdog, auto-responder, event router
• Circuit breaker + Dead Letter Queue per agent
• Dream Engine for nightly consolidation
• Complementary to Google A2A (local vs remote)

Integration path

1. Register as MCP server in config.yaml
2. Plugin defines crons (amb-message-router, amb-watchdog)
3. Built-in agent_discover() + send_bus_message() tools

Links

• Repo: https://github.com/kriszmac4/a2a-communication-protocol
• Docs: https://github.com/kriszmac4/a2a-communication-protocol/tree/main/docs
• SCP companion: https://github.com/kriszmac4/scp
• Release: https://github.com/kriszmac4/a2a-communication-protocol/releases/tag/v1.0.0

[teknium1]

Thanks for publishing the Agent Message Bus and documenting its MCP/cron design. This is an automated hermes-sweeper review.

• The proposal is for an official integration of the external kriszmac4/a2a-communication-protocol project, including built-in Hermes-facing tools.
• Hermes policy does not accept new third-party product integrations under this repository's plugins/ tree; they should ship as standalone plugins installed under ~/.hermes/plugins/ or via a pip entry point (AGENTS.md:797-810). This is a maintenance/coupling decision, not a judgment of the project.
• Hermes already supports the proposed MCP route: configure an external server under mcp_servers in config.yaml, after which its tools are discovered automatically (website/docs/user-guide/features/mcp.md:7-48).
• The later cross-reference to feat(plugins): inter-plugin event bus with declared emits/listens contracts #64164 concerns a distinct, in-process plugin event bus; its stated non-goals explicitly keep cross-process/multi-profile messaging such as Proposal: Agent Message Bus (A2A plugin) for official Hermes integration #42349 separate.

Please continue this as a standalone plugin and/or MCP service, and share it through #plugins-skills-and-skins rather than adding it to the Hermes core tree.

---

Closed as not-planned per standing maintainer policy (in-tree-provider-integration). This is a design-direction decision, not a code-quality judgment — see the Contribution Rubric in AGENTS.md for what the project is looking for. If you believe this policy was misapplied to your change, comment here and a maintainer will take a look.