NousResearch/hermes-agent

MCP OAuth browser callback not captured correctly

Cluster 116278. Data as of 2026-10-26 12:29 UTC

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

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

Read #116658 Pick up a Lab task

A bug where the MCP login flow fails to register the OAuth callback despite the browser reaching the correct loopback port, apparently because subsequent browser requests (e.g. favicon.ico) overwrite or interfere with the first callback result. The members include the bug report and two related fix attempts.

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.

#116658 fix(mcp): browser OAuth callback is registered even when the browser also fetches favicon.ico (#116278, salvage #116314)

merged to main

files: tests/tools/test_mcp_oauth_callback_latch.py, tools/mcp_oauth.py

1 PR closed without merging

From the close comments: merged via another change 1

#116314 fix(mcp): keep the first callback result from being clobbered by browser fetches · merged via another change → 74ddb73, #116658, #116278, #116314

Closed issues · 1

Closed#116278mcp login: browser callback reaches the correct loopback port but the waiting flow never registers it (code+state+iss verified in browser history; curl to the same socket works)

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

For your agent

The same facts, typed.

cluster/116278.json
cluster/116278.md