Cairn
NousResearch/hermes-agent

MCP OAuth start_flow error misreported as timeout

Cluster 105251 · mcp. Data as of

2 open items. Fix attempted, not merged.

The short answer

0open issues
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 2 PRs.

These issues and PRs address a bug where real errors from MCP OAuth start_flow() are incorrectly surfaced as timeout errors. The work focuses on preserving and accurately reporting the underlying error instead of masking it with a generic timeout message.

Open issues0

No open issues.

Open PRs2

  • PR#105254fix(gateway): surface real MCP OAuth start_flow() errors instead of blanket timeout
  • PR#105278fix(tui): preserve MCP OAuth startup errors

1 PR closed without merging

From the close comments: other 1

  • #105253 Fix: MCP OAuth start_flow mislabels real errors as timeout · other
Closed issues · 1
  • Closed#105251tui_gateway: MCP OAuth start_flow() mislabels real errors as "Timed out"
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

Subsystem
mcp
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/105251.json
cluster/105251.md