Cairn
NousResearch/hermes-agent

Stale API key cleanup on provider switch

Cluster 14134 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

These issues and pull requests address a bug where API keys from a previous provider persist incorrectly after switching providers. The work focuses on clearing stale API key state during provider transitions.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1 · other 1

  • #14370 fix: clear stale api_key on provider switch · other → #14134
  • #14373 fix: clear stale api keys when switching API-key providers · done elsewhere → #14134
  • #18906 fix: clear stale api_key on provider switch · superseded by another PR → #14373, #14134
Closed issues · 1
  • Closed#14134[Bug]: api_key drift on provider switch — real Hermes bug
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
hermes cli
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/14134.json
cluster/14134.md