Cairn
NousResearch/hermes-agent

Enum-style reasoning_effort 400 error matching fixes

Cluster 115277 · agent. Data as of

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

These items address cases where enum-style or structured reasoning_effort values trigger 400 errors that are not correctly matched by the existing rejection/retry logic. Fixes span agent, auxiliary, and commandcode relay contexts.

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.

  • #115736 fix(agent): enum-style and structured reasoning_effort 400s recover instead of failing or compressing (#115277, #100536, salvage #115281)

    merged to main

    files: agent/chat_completion_helpers.py, agent/error_classifier.py, agent/turn_recovery.py, tests/agent/test_auxiliary_parameter_rung_chaining.py, tests/agent/test_error_classifier.py, tests/agent/test_reasoning_disable_recovery.py

2 PRs closed without merging

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

  • #115281 fix(agent): match enum-style reasoning_effort rejections with no unsupported marker · merged via another change → 4749025, #115736, #115277, #100536, #115281
  • #115308 fix(auxiliary): match enum-style reasoning_effort 400 as a field rejection · other
Closed issues · 1
  • Closed#115277[Bug]: commandcode relay's "Invalid option: expected one of ..." 400 for reasoning_effort "none" is not matched by the reasoning-rejection retry ladder
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

Subsystem
agent
Merged PRs
#115736
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
19 Sep 2026

For your agent

The same facts, typed.

cluster/115277.json
cluster/115277.md