NousResearch/hermes-agent

Priority ordering for pooled auth credentials

Cluster 104638. Data as of 2026-10-25 11:21 UTC

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

open issues

open PRs

items grouped

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

Next step: read #104910, then check it covers your case.

Read #104910 Pick up a Lab task

These items concern adding priority controls to credential pooling, allowing individual pooled credentials to be placed or recovered according to a specified fill-first order.

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.

#104910 feat: recover and prioritize individual pooled credentials (salvage #104660–#104664)

merged to main

files: agent/credential_pool.py, agent/credential_pool_admin.py, contributors/emails/[redacted:email], evals/auth_pool_controls.py, hermes_cli/_parser.py, hermes_cli/auth_commands.py, hermes_cli/console_engine.py, hermes_cli/subcommands/auth.py, hermes_cli/tips.py, tests/agent/test_credential_pool_operations.py, tests/hermes_cli/test_auth_pool_operations.py, website/docs/reference/cli-commands.md, website/docs/user-guide/features/credential-pools.md

1 PR closed without merging

From the close comments: merged via another change 1

#104664 feat(auth): place pooled credentials by priority · merged via another change → 1a4bb74, 12ad29a, de25786, #104910, #104660, #104664, #104638

Closed issues · 1

Closed#104638[Feature]: hermes auth add --priority and hermes auth priority to place a credential in the fill_first order

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.67: 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

Merged PRs: #104910
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 7 Sep 2026

For your agent

The same facts, typed.

cluster/104638.json
cluster/104638.md