NousResearch/hermes-agent

OAuth credential not persisted in named profiles

Cluster 120177 · agent. Data as of

Nothing open on GitHub. Fix merged in #134574 on 7 Oct 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #134574. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #134574. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes address a bug where adding a first single-use OAuth credential to a named profile appeared to succeed but was silently dropped rather than saved. The work targets profile-scoped auth persistence when the root credential store is empty.

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.

  • #134574 fix(auth): a profile's own auth add login is saved and kept, never forking root's grant (salvage #126551)

    merged to main

    files: agent/credential_pool.py, agent/credential_pool_admin.py, hermes_cli/auth_commands.py, hermes_cli/auth_oauth_grants.py, tests/agent/test_credential_pool_profile_oauth_fork.py, website/docs/user-guide/profiles.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/profiles.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #120210 fix(auth): persist first single-use OAuth add to the named profile · superseded by another PR → #120177, #134574, #101827
  • #126551 fix(auth): profile-scoped auth add with an empty root saves the credential instead of dropping it (salvage #103712 + #101827) · merged via another change → #134574, #101827
Closed issues · 1
  • Closed#120177[Bug]: First Codex OAuth credential in a named profile reports success but is not persisted
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
Merged PRs
#134574
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
7 Oct 2026

For your agent

The same facts, typed.