NousResearch/hermes-agent

MCP dashboard OAuth flow ending causes server parking

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

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

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

Read #117060 Pick up a Lab task

These issues and PRs address a bug where an ended or expired dashboard OAuth flow causes the MCP server to be permanently parked rather than retrying or re-minting the OAuth attempt. The work focuses on correctly classifying and handling the ended OAuth flow state.

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.

#117060 fix(mcp): an expired dashboard OAuth attempt is re-minted on retry instead of parking the MCP server (#114739, salvage #114913)

merged to main

files: hermes_cli/web_routers/mcp.py, tests/hermes_cli/test_mcp_dashboard_oauth.py, tests/tools/test_mcp_dashboard_oauth.py, tools/mcp_dashboard_oauth.py, tui_gateway/mcp_oauth_sessions.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

#114763 fix(mcp): classify an ended dashboard OAuth flow as a permanent auth failure · done elsewhere → 1d0c580, #117060, #114739, #114913
#114913 fix(mcp): an ended dashboard OAuth flow is re-minted for the retry instead of parking the server · merged via another change → 1d0c580, #117060, #114739, #114913

Closed issues · 1

Closed#114739[Bug]: RuntimeError('OAuth flow already ended') in mcp_dashboard_oauth.publish_authorization_url parks an OAuth MCP server permanently

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

For your agent

The same facts, typed.

cluster/114739.json
cluster/114739.md