NousResearch/hermes-agent

MCP credential isolation bug across dashboard profiles

Cluster 111151. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #111481 on 15 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 #111481. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #111481. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #111481 Pick up a Lab task

A bug where dashboard-served profile sessions incorrectly used another profile's MCP credentials due to improper connection scoping. These items address isolating MCP secrets, connections, and credentials per profile in dashboard contexts.

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.

#111481 fix(mcp): dashboard-served profiles keep their own MCP connections and credentials (#111151)

merged to main

files: agent/secret_scope.py, tests/tools/test_mcp_multiplex_connection_keys.py, tools/mcp_tool.py, tools/registry.py, website/docs/user-guide/multi-profile-gateways.md

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

#111158 fix(dashboard): scope MCP secrets per profile · other → 57c4e1d, #111481, #111158, #111151
#111354 fix(mcp): isolate dashboard-served profile connections without global multiplex flag · done elsewhere → 57c4e1d, 5117e3b, #111481, #111151

Closed issues · 1

Closed#111151[Bug]: Dashboard-served profile sessions call MCP servers with another profile's credentials (multiplex scope never active on hermes_cli surfaces)

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.50: 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: #111481
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 15 Sep 2026

For your agent

The same facts, typed.

cluster/111151.json
cluster/111151.md