NousResearch/hermes-agent

MCP cross-profile connection identity adoption bug

Cluster 122665. Data as of 2026-10-24 13:18 UTC

Nothing open on GitHub. Fix merged in #124119 on 26 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #124119, then check it covers your case.

Read #124119 Pick up a Lab task

A bug where multiplexed profiles incorrectly adopt MCP connections opened under a different profile's identity or secret-source environment. The fixes enforce that a profile only adopts a shared connection when the computed identity matches its own.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

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

#124119 fix(mcp): a profile only adopts a shared connection whose resolved identity matches its own

merged to main

files: tests/gateway/test_multiplex_mcp_discovery.py, tests/tools/test_mcp_multiplex_connection_keys.py, tests/tools/test_mcp_shared_connection_resolved_identity.py, tools/mcp_tool.py, tools/mcp_tool_registration.py, tools/mcp_tool_server_run.py, tools/mcp_tool_transport.py

2 PRs closed without merging

From the close comments: done elsewhere 2

#122666 fix(mcp): a profile only adopts a shared connection whose resolved identity matches its own · done elsewhere → 684f7e9, #124119
#123233 fix(mcp): compare effective connection inputs before cross-profile adoption · done elsewhere → 684f7e9, #124119

Closed issues · 1

Closed#122665[Bug]: multiplexed profiles adopt another profile's MCP connection opened with that profile's secret-source env / identity header

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

Merged PRs: #124119
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 26 Sep 2026

For your agent

The same facts, typed.

cluster/122665.json
cluster/122665.md