You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Anthropic default claude-sonnet-4-5 refuses every request today (temperature with top_p, HTTP 400); it retires 30 Nov and claude-sonnet-5-5 refuses the temperature #874
The Anthropic default fails today. With Anthropic selected, the model is claude-sonnet-4-5-20250929 (api/config.py:126), and run_completion sends top_p: 1 with every caller's temperature (api/agents/utils.py:172; LiteLLM 1.108.3 from uv.lock forwards both). Sent live on 9 Nov in the shape of the relevancy check, the first call of every question (api/agents/relevancy_agent.py:90-94): HTTP 400 "temperature and top_p cannot both be specified for this model. Please use only one." The database description made on connect (api/utils.py:158-167) gets the same 400.
The replacement refuses it too. Anthropic retires that model on 30 November 2026 and names claude-sonnet-5-5 (model deprecations). Sent to Anthropic, the same request on claude-sonnet-5-5 returns HTTP 400 "temperature is deprecated for this model."; the pinned LiteLLM stops it before sending.
Users see a generic error. The Settings key check sends neither setting (api/routes/settings.py:83-95), so both models pass it; every question then ends in "Internal error while processing query" (api/routes/graphs.py:268-287). Settings offers claude-sonnet-4-5-20250929 as the Anthropic example (app/src/utils/vendorConfig.ts:13).
I sent the requests with invented text, not through QueryWeaver.
I'm Lakshya; I'm building a tool that checks model migrations on a team's real requests.
Activity