NousResearch/hermes-agent

Auth bootstrap fails to recognize custom/openrouter providers

Cluster 109397. Data as of 2026-10-24 04:06 UTC

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

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #118321. 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 #118321, then check it covers your case.

Read #118321 Pick up a Lab task

A regression in boot/inventory logic caused custom and OpenRouter model providers to be unrecognized during bootstrap, triggering a spurious 'needs a model provider' error. Multiple fix attempts target the provider detection logic in auth configuration.

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.

#118321 fix(auth): boot inventory recognises model.provider openrouter and bare providers: pins (salvage of #114351)

merged to main

files: contributors/emails/[redacted:email], hermes_cli/auth.py, tests/hermes_cli/test_resolve_provider_custom_endpoint.py

2 PRs closed without merging

From the close comments: merged via another change 1 · other 1

#109416 fix(auth): recognize custom and openrouter in _config_model_provider for bootstrap (#109397) · other → #109256, #109072
#114351 fix(auth): recognise model.provider openrouter in boot inventory · merged via another change → 34ad35e, #118321, #109416, #109256

Closed issues · 1

Closed#109397[Bug]: Dashboard TUI shows "Hermes needs a model provider before the TUI can start a session" for `provider: custom` installs (0.21.2 free-tier bootstrap regression)

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

Merged PRs: #118321
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 21 Sep 2026

For your agent

The same facts, typed.

cluster/109397.json
cluster/109397.md