NousResearch/hermes-agent

Named custom provider routing in codex app server

Cluster 75186 · agent. Data as of 2026-10-29 11:48 UTC

Nothing open on GitHub. Fix merged in #115905 on 19 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 #115905. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #115905. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #115905 Pick up a Lab task

These issues and pull requests concern adding support for named custom providers within the codex_app_server runtime. The work involves enabling the app server to correctly route requests to named custom providers.

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.

#115905 feat(codex): named custom providers work with the codex_app_server runtime (#75186, salvage #75191)

merged to main

files: agent/codex_runtime.py, agent/transports/codex_app_server_session.py, hermes_cli/runtime_provider.py, hermes_cli/runtime_provider_custom.py, tests/agent/transports/test_codex_app_server_session.py, tests/hermes_cli/test_runtime_provider_resolution.py, tui_gateway/server.py, website/docs/reference/slash-commands.md, website/docs/user-guide/features/codex-app-server-runtime.md

1 PR closed without merging

From the close comments: merged via another change 1

#75191 [codex] support named custom app-server providers · merged via another change → f0d8efe, #115905, #75186, #75191

Closed issues · 1

Closed#75186codex_app_server cannot route named custom providers

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

Subsystem: agent
Merged PRs: #115905
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/75186.json
cluster/75186.md