Title generation sends unsupported reasoning_effort to custom endpoints
Cluster 112781. Data as of
Nothing open on GitHub. Fix merged in #113958 on 17 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113958. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113114. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where auxiliary title generation incorrectly forwards the reasoning_effort parameter to custom or OpenAI-compatible endpoints that don't support it, causing HTTP 400 errors. Multiple fix attempts address omitting or recovering from this parameter rejection on primary and fallback routes.
Open issues0
Open PRs0
Fixes on record
-
#113114 fix(aux): title generation survives custom endpoints that reject reasoning_effort (#112781, supersedes #112789)
files:
agent/auxiliary_client.py,tests/agent/test_auxiliary_reasoning_field_rejection_retry.py,website/docs/user-guide/configuration.md,website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/configuration.md -
#113958 fix(aux): title generation recovers from stacked parameter rejections on primary and fallback routes (#78273, #72351, #109774, salvage #72515)
files:
agent/auxiliary_client.py,agent/auxiliary_fallback_recovery.py,agent/title_generator.py,plugins/model-providers/fireworks/__init__.py,tests/agent/test_auxiliary_parameter_rung_chaining.py,tests/plugins/model_providers/test_fireworks_profile.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#112789 fix(agent): omit reasoning effort for custom title routes · done elsewhere →
cbe2413,#113958,#83390
Closed issues · 1
- Closed#112781[Bug]: Auxiliary title_generation sends top-level `reasoning_effort` on custom/OpenAI-compatible endpoints - HTTP 400 on models that don't support it
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.00means 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