NousResearch/hermes-agent

Multiplexed gateway MCP server profile visibility bug

Cluster 105396. Data as of 2026-10-25 11:21 UTC

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

open issues

open PRs

items grouped

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

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

Read #106314 Pick up a Lab task

A bug where non-default profiles in a multiplexed gateway cannot see or call MCP server tools, particularly after profile reloads, along with related fix attempts addressing scope-tagging and shared MCP server visibility.

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.

#106314 fix(gateway): a multiplexed profile sharing an MCP server sees and can call its tools (#105396; salvage #105542)

merged to main

files: gateway/run_turn.py, tests/gateway/test_multiplex_mcp_discovery.py, tools/mcp_tool.py, tools/mcp_tool_discovery.py, tools/mcp_tool_health.py, tools/mcp_tool_lifecycle.py, tools/mcp_tool_registration.py, tools/mcp_tool_server_run.py

1 PR closed without merging

From the close comments: done elsewhere 1

#105542 fix(gateway): preserve shared MCP visibility across profile reloads · done elsewhere → 4ddbcbd, #106314

Closed issues · 1

Closed#105396[Bug]: Multiplexed gateway starves non-default profiles of MCP servers — scope-tagging tied to name-keyed discovery, every /reload-mcp on a non-default profile reports 'No MCP servers connected'

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: #106314
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 9 Sep 2026

For your agent

The same facts, typed.

cluster/105396.json
cluster/105396.md