What this error means

API Error 400: messages.N.content.M: thinking or redacted_thinking blocks in the latest assistant message cannot be modified. These blocks must remain as they were in the original response. is a Claude Code failure pattern reported for developers trying to fix claude code opus 4.8 api 400 error caused by thinking/redacted_thinking block modification during subsequent api calls. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Open GitHub issue #63607 on anthropics/claude-code filed 2026-05-29T10:39Z. Labelled bug+duplicate+area:core+api:anthropic. Multiple related issues (#63608, #63606) report the same underlying thinking block modification problem. This affects paid Anthropic API users and Claude Code subscription users — strong commercial value. Category maps to AI Coding Tools per SKILL.md rules.

Common causes

  • Open GitHub issue #63607 on anthropics/claude-code filed 2026-05-29T10:39Z. Labelled bug+duplicate+area:core+api:anthropic. Multiple related issues (#63608, #63606) report the same underlying thinking block modification problem. This affects paid Anthropic API users and Claude Code subscription users — strong commercial value. Category maps to AI Coding Tools per SKILL.md rules.

Quick fixes

  1. Confirm the exact error signature matches API Error 400: messages.N.content.M: thinking or redacted_thinking blocks in the latest assistant message cannot be modified. These blocks must remain as they were in the original response..
  2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
  3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

  • Verify the command, editor, extension, or API client that produced the error.
  • Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
  • Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

  • Keep provider/tool configuration documented.
  • Record non-secret diagnostics such as tool version, provider name, model name, and command path.
  • Add a lightweight check before CI or production workflows depend on the tool.