NousResearch/hermes-agent

OpenAI auxiliary provider routing and fallback fixes

Cluster 116055. Data as of

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

The short answer

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

These items address a bug where the 'openai' auxiliary provider alias resolves inconsistently across auxiliary paths, with background_review silently falling back to the main model. The work covers identifying dead review routes, fixing the alias resolution, and elevating silent fallback behavior to a visible log.

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.

  • #116346 auxiliary provider "openai" routes identically on every aux path; dead review routes are reported (#116055, salvage #116083)

    merged to main

    files: agent/auxiliary_client.py, agent/background_review.py, agent/curator.py, agent/moa_loop.py, hermes_cli/doctor_config.py, hermes_cli/runtime_provider.py, hermes_cli/runtime_provider_custom.py, tests/agent/test_aux_session_endpoint_affinity.py, tests/agent/test_background_review_cost_controls.py, tests/agent/test_multiplex_base_url_scope.py, tests/hermes_cli/test_doctor.py, tests/hermes_cli/test_runtime_provider_resolution.py, website/docs/user-guide/configuration.md

1 PR closed without merging

From the close comments: done elsewhere 1

  • #116083 fix(cli): resolve auxiliary openai provider alias and elevate fallback log · done elsewhere → 8e0828a, #116346
Closed issues · 1
  • Closed#116055[Bug]: auxiliary provider "openai" resolves differently on the two aux paths — background_review silently falls back to the main model
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
#116346
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
19 Sep 2026

For your agent

The same facts, typed.