Cairn
NousResearch/hermes-agent

A2A multiplexed profile scoping and port binding

Cluster 122126 · gateway. Data as of

1 open item. Fix merged in #126160 on 28 Sep 2026. Check it covers your case.

The short answer

0open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #126160. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #126160. That is separate from the fix event.
Still open
0 issues and 1 PR.

These items address bugs and fixes in A2A server behavior under multiplexed profiles, covering port binding conflicts and ensuring per-profile scoping of gates, config, and related components.

Open issues0

No open issues.

Open PRs1

  • PR#122128fix(a2a): resolve the inbound enablement gate through the profile-scoped reader

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #126160 Multiplex secondary profiles keep their A2A gate, Buzz config, plugin injector, MCP headers, describe and tools.list scoped to the served profile (#122126 #125985 #125102 #119092 #120726 #117977)

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], gateway/run_inbound.py, hermes_cli/plugins.py, plugins/platforms/a2a/__init__.py, plugins/platforms/a2a/tools.py, plugins/platforms/buzz/adapter.py, tests/gateway/test_buzz_adapter.py, tests/gateway/test_plugin_message_injection.py, tests/hermes_cli/test_plugin_message_injection.py, tests/plugins/test_a2a_plugin.py, tests/tools/test_mcp_connect_secret_scope.py, tests/tui_gateway/test_profiles_describe_secret_scope.py, tests/tui_gateway/test_tools_readback_scope.py, tools/mcp_tool_config.py, tools/mcp_tool_discovery.py, tools/mcp_tool_server_run.py, tui_gateway/methods_profiles.py, tui_gateway/methods_tools.py, website/docs/developer-guide/multiplexing-gateway.md (+1 more)

Closed issues · 1
  • Closed#122126[Bug]: A2A inbound server binds the same port in every multiplexed profile (one wins, N-1 go `bind_failed`)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Merged PRs
#126160
Closed issues
1
Attempts
0 PRs closed without merging
Fix link checked
28 Sep 2026

For your agent

The same facts, typed.

cluster/122126.json
cluster/122126.md