Cairn
NousResearch/hermes-agent

Codex proxied routes resolving wrong context window size

Cluster 116191. Data as of

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

These issues and PRs concern proxied or custom-endpoint Codex routes incorrectly resolving the larger 1.05M direct-API context window instead of the correct 272K Codex OAuth window, causing compression to trigger too late. The work focuses on fixing model metadata resolution for these custom routes.

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.

  • #116329 fix(context): proxied Codex routes (custom codex_responses provider, HERMES_CODEX_BASE_URL) resolve the 272K Codex window, not the 1.05M direct-API catalog (#116191, credit #116199 #116262)

    merged to main

    files: agent/model_metadata.py, hermes_cli/config.py, hermes_cli/config_providers.py, tests/agent/test_model_metadata.py, website/docs/integrations/providers.md

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #116199 fix(context): resolve Codex OAuth window for codex_responses custom endpoints · done elsewhere → 1372de3, #116329
  • #116262 fix(model-metadata): resolve Codex context on custom routes · done elsewhere → 1372de3, #116329
Closed issues · 1
  • Closed#116191Proxied Codex models resolve the 1.05M API context window instead of the 272K Codex OAuth window, so compression fires ~2x past the Codex limit
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
#116329
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
19 Sep 2026

For your agent

The same facts, typed.

cluster/116191.json
cluster/116191.md