Cairn
NousResearch/hermes-agent

Authentication and API key handling across several providers

Cluster 55539 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues 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
1 issue and 2 PRs.

These members share a loose authentication/API-key theme but touch different areas: Anthropic OAuth token endpoint iteration, a config.yaml api_key fallback, a Kanban worker Authorization header issue with a minimax-cn profile, and masked key display in request dumps. They may not describe a single shared problem.

Open issues1

  • Issue#55539[Kanban] Worker spawn produces Authorization: Bearer *** on first LLM call for minimax-cn profile

Open PRs2

  • PR#55552fix(diagnostics): show masked API key and correct URL in request dumps for anthropic_messages mode
  • PR#55587fix(auth): add config.yaml model.api_key fallback for API-key providers

1 PR closed without merging

From the close comments: won't fix / by design 1

  • #45254 fix(auth): iterate token endpoints in Anthropic OAuth login flow · won't fix / by design
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/55539.json
cluster/55539.md