OAuth authentication bugs and fixes for Qwen/MCP

NousResearch/hermes-agent · cluster 7746 · agent

Data as of

6 open items. Fix attempted, not merged.

The short answer

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

Multiple bug reports and fix attempts addressing OAuth token exchange failures, including issues with response content types, missing headers, redirect handling, and compatibility with newer Qwen CLI authentication methods.

Open issues3

  • Issue#7746[Bug]: qwen-oauth refresh fails with invalid JSON, while the same ~/.qwen/oauth_creds.json works in qwen-code-api
  • Issue#44592OAuth token exchange fails when server returns application/x-www-form-urlencoded
  • Issue#46771[Bug]: Hermes appears incompatible with modern Qwen CLI authentication.

Open PRs3

  • PR#28244fix(qwen-oauth): add follow_redirects=True and diagnostic logging
  • PR#44605Fix MCP OAuth token exchange Accept header
  • PR#46851fix(auth): support modern Qwen CLI v0.18+ API-key authentication

4 PRs closed without merging

From the close comments: closed without comment 2 · superseded by another PR 1 · other 1

  • #7751 fix(auth): add User-Agent header to Qwen OAuth refresh (closes #7746) · closed without comment
  • #7782 fix(qwen): add User-Agent to OAuth refresh request · other
  • #45552 fix(mcp-oauth): handle form-encoded OAuth token responses · superseded by another PR
  • #124247 fix(qwen-oauth): match qwen-code-api User-Agent and surface invalid-JSON diagnostics (#7746) · closed without comment
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.19: 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
agent
Closed issues
0
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.