Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.282 ·

Rejected redacted thinking data is now handled like a bad thinking signature

Claude Code now treats the API's "invalid data in redacted_thinking block" error the same way as a thinking signature error

You'll notice Bug Fixes
JSON All of v2.1.282
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ThinkingArea: what it touches
Bug FixesKind: in v2.1.282,
Bug FixesSection of the release
What

Thinking is the reasoning the model does before it answers. Some of it can come back in hidden form, called a redacted_thinking block. When the API rejects a request with an error whose message contains "invalid data in redacted_thinking block", Claude Code now classes it as a thinking_signature error. That is the same category it already used for errors about bad or missing thinking signatures, and it goes through the same handling. This applies to everyone.

Why

A session that hits corrupted redacted thinking data should now be handled the same way as one that hits a signature error, instead of failing outright.

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 doubtWhat Claude Code does after classing the error, such as removing the thinking and retrying, is not confirmed.
Anthropic's release notes agreeFixed sessions failing on every turn with an "Invalid data in redacted_thinking block" API error; Claude Code now drops the conversation's…

See this entry in the whole of v2.1.282 →

Feedback