NousResearch/hermes-agent

'max' reasoning effort mangled on custom OpenAI-compatible relays

Cluster 114249. Data as of 2026-10-26 12:29 UTC

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

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

Read #114808 Pick up a Lab task

A bug where the reasoning effort value 'max' is silently rewritten to 'xhigh' when using custom OpenAI-compatible relays in Responses/Codex API mode. The cluster includes the bug report and related fix attempts addressing vocabulary declaration for this effort level.

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.

#114808 fix(codex): a configured max reasoning effort reaches custom Responses relays instead of xhigh (#114249, salvage #114255)

merged to main

files: agent/transports/codex.py, plugins/model-providers/custom/__init__.py, tests/agent/transports/test_router_codex_efforts.py, tests/plugins/model_providers/test_custom_profile.py, website/docs/integrations/providers.md

1 PR closed without merging

From the close comments: merged via another change 1

#114255 fix(custom): declare the OpenAI-compat effort vocabulary so Responses keeps a configured max · merged via another change → d7f2644, #114808, #114249, #114255

Closed issues · 1

Closed#114249[Bug]: reasoning effort "max" is silently rewritten to "xhigh" on custom OpenAI-compatible relays (api_mode: codex_responses)

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: #114808
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/114249.json
cluster/114249.md