## TL;DR

Pass every thinking and redacted\_thinking block back exactly as received, in order, including blocks whose thinking field is empty. If you filter content blocks by type anywhere, add both thinking types to the allowlist.

## Steps

1. The most recent assistant message's `thinking` or `redacted_thinking` blocks were edited, reordered, filtered out, or reconstructed before being sent back. Common trigger: application code that filters content blocks by type (keeping text and tool_use) and silently drops the thinking blocks.

2. Pass every `thinking` and `redacted_thinking` block back exactly as received, in order, including blocks whose thinking field is empty.
2. If you filter content blocks by type anywhere, add both thinking types to the allowlist.
3. Do not regenerate or "clean up" thinking content; the signature check rejects anything but the original bytes.

3. Resend the identical conversation with the blocks preserved and the 400 is gone. The error names the exact position, so the fix is confirmed at the named block.

## When to use

You are seeing this: 400 invalid\_request\_error, message starts with a block position like messages.1.content.0 and complains about thinking blocks. Use this skill when you run into "Anthropic 400 naming messages.N.content.M: you edited or filtered thinking blocks before resending them".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The most recent assistant message's thinking or redacted\_thinking blocks were edited, reordered, filtered out, or reconstructed before being sent back.