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

Claude Code v2.1.304 ·

API refusals now count as a trigger alongside retries and successes

A check that already reacted to accelerated retries and successful API responses now also reacts to API refusals

Under the hood Internal Changes
JSON All of v2.1.304
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
APIArea: what it touches
Internal ChangesKind: in v2.1.304,
Internal ChangesSection of the release

Unclear It is not clear what this check controls, so what a refusal now changes for a user is unknown.

What

Claude Code has an internal check that reacts to certain events when it talks to the API, the service that runs the model. That check already matched an accelerated retry and a successful response. It now also matches a refusal, meaning a request the API declined to answer.

Why

Refusals from the API are now handled the same way as those other two events wherever this check is used.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what this check controls, so what a refusal now changes for a user is unknown.

See this entry in the whole of v2.1.304 →

Feedback