* refactor(plugins): remove the Sep 2026 decomposition compat layer on schedule The PLUGIN-COMPAT layer (2776813df3+d63e380324+0a5164cebe) kept pre-#102117 import paths alive for external plugins until 2026-09-14. That window closed two weeks ago; since then the loader has already been skipping plugins that use the old paths. This removes the layer itself: - 328 appended `PLUGIN-COMPAT` blocks (lazy `__getattr__` pointer tables, re-exported third-party names, restored dead definitions) and the three re-export stub modules (gateway/startup_watchdog, hermes_cli/observability/relay_runtime, tools/environments/modal_utils) - COMPAT_MANIFEST.md, compat_manifest.json, scripts/check_compat_pointers.py and its lint step - the reporting surfaces: CLI banner notice, `hermes plugins compat`, the `hermes doctor` section, the post-update notice, the Desktop one-time dialog, the loader's pre-import skip and the `plugins.allow_deprecated_imports` escape hatch An external plugin that still imports an old path now fails to load with its ImportError as the reason in `hermes plugins list`, the same path as any broken plugin. hermes_cli/plugin_compat.py stays as three inert stubs (compat_report, removal_in_effect, summary_lines): an already-running pre-removal `hermes update` lazy-imports them after the checkout swap (tests/compat/old_updater_surface.json). In-tree fallout, both already dead: hermes_cli/setup.py::_check_espeak_ng (no callers; its `shutil` came from a compat block) and gateway/config.py::SessionResetPolicy ("retained solely for the scheduled plugin-compat window"). Two test_run_agent patches targeted the removed `run_agent.handle_function_call` pointer; they now patch `model_tools.handle_function_call`, the seam production reads, like every sibling test in that file. * chore: retrigger CI (zero-job startup_failure phantom) * test: drop resolution allowlist rows for the two deleted which() sites hermes_cli/setup.py::_check_espeak_ng (dead) and tools/skillevaluator_scan.py::scanner_available (a restored definition inside a PLUGIN-COMPAT block) no longer exist; the stale-row gate requires their allowlist entries go with them.
A2A — Agent-to-Agent protocol for Hermes
Talk to other agents, and let other agents talk to you, over the open
A2A protocol v1.0. Works with any A2A-compliant
peer (another Hermes, LangChain, CrewAI, Google ADK, OpenClaw, …). Stdlib only —
no a2a-sdk dependency.
Enable
hermes gateway setup # pick A2A, or:
# ~/.hermes/config.yaml
gateway:
platforms:
a2a:
enabled: true
extra:
port: 9900
# peers you want to call (outbound):
a2a_agents:
researcher:
url: "http://localhost:9999"
auth: { type: bearer, token: "sk-..." }
timeout: 120
capabilities: [web_search, research]
Outbound — call other agents
The agent gets five tools:
a2a_discover(url)— what can this agent do?a2a_call(agent, message, context_id?)— send it a task, get the reply.a2a_list()— configured peers, saved conversations, metrics.a2a_history(context_id)— recall a saved A2A conversation.a2a_orchestrate(capability, message, mode?)— fan-out a task to every peer advertising a capability (all/first/best).
Inbound — be callable
When the a2a platform is enabled, Hermes serves a v1.0 Agent Card at
http://<host>:<port>/.well-known/agent-card.json (the legacy
/.well-known/agent.json path is also answered for pre-1.0 clients) and
accepts JSON-RPC
message/send, message/stream (SSE), tasks/get|list|cancel|subscribe,
and push notification configs (inline or via
tasks/pushNotificationConfig/create). Incoming tasks are injected into your
live agent session — the same agent that's talking to you, with full
memory — and the reply is returned over A2A. Completed tasks stay queryable
via tasks/get.
Security
- No token ⇒ localhost only. The server binds
127.0.0.1and refuses to widen unless you configure a token and setA2A_HOST. - Per-peer tokens:
A2A_PEER_TOKENS="alice:tok1,bob:tok2"gives each remote agent its own credential; that authenticated name (never anything in the request body) drives rate limiting, trust, and audit. - Inbound text — including
/-prefixed text — is run through prompt-injection filters and framed as untrusted peer input; remote peers cannot invoke operator slash commands. - Outbound text is scrubbed of credential-shaped strings.
- Push callbacks are SSRF-guarded and HMAC-SHA256 signed (
X-A2A-Signature). - Every exchange is logged to
~/.hermes/a2a_audit.jsonl. - Conversations persist to
~/.hermes/a2a_conversations/— they survive context compaction and restarts (a2a_historyrecalls them).
Env vars
| Var | Default | Meaning |
|---|---|---|
A2A_PEER_TOKENS |
(unset) | Per-peer credentials name:token,… (preferred). |
A2A_BEARER_TOKEN |
(unset) | Shared token; identity falls back to caller IP. |
A2A_HOST |
127.0.0.1 |
Bind host. Only widens with a token set. |
A2A_PORT |
9900 |
Inbound port. |
A2A_AGENT_NAME |
hostname-derived | Name on the Agent Card. |
A2A_PUBLIC_URL |
(unset) | Routable URL advertised on the card (reverse proxies). |
A2A_TRUSTED_PEERS |
(unset) | Allow-list of authenticated identities. |
A2A_ALLOW_ALL_USERS |
false |
Allow any authed peer (dev only). |
A2A_RATE_LIMIT |
60 |
Requests/minute per identity. |
A2A_MAX_PINGPONG_TURNS |
5 |
Anti-loop turn cap per context (max 20). |
A2A_REPLY_TIMEOUT |
300 |
Seconds to wait for the agent's reply; the orphan sweep never fails a task before this window (floor 300s) or while a request still waits on it. |
A2A_PUSH_SECRET |
bearer token | HMAC secret for push signing. |
A2A_ADVERTISED_TOOLSETS |
all registered | Restrict skills on the Agent Card. |
See DESIGN.md for architecture and the requirement-tracing table.