Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.305 ·

Failed model changes now report a more specific reason

When a controlling program's request to change the model fails, Claude Code now reports a finer reason, such as rate limit or failed sign-in

You'll notice Improvements
JSON All of v2.1.305
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SDKArea: what it touches
ImprovementsKind: in v2.1.305,
ImprovementsSection of the release
What

A program that drives Claude Code, such as one built with the SDK (the toolkit for building on Claude Code), can ask it to switch models. When that request fails, the reason it gets back is now more specific. The listed reasons are:

  • not_found
  • check_rejected, when the API returned an error that no retry or sign-in clears
  • credits_required
  • rate_limit
  • auth_failed
  • verdict_pending, which is not a refusal: the outcome follows as a separate informational message
  • internal_error

These reasons also cover settings changes sent through apply_flag_settings. Sign-in errors, errors a retry will not fix, and rate limits (too many requests) are now told apart. A "forbidden" error is treated as worth retrying only when CLAUDE_CODE_REMOTE is set or the session is otherwise remote.

Why

Programs that control Claude Code can now tell why a model change failed and react to it, for example by waiting out a rate limit or asking the user to sign in again.

See this entry in the whole of v2.1.305 →

Feedback