claude-code - 💡(How to fix) Fix [BUG] API Error: 400 — thinking or redacted_thinking blocks in the latest assistant message cannot be modified.

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Claude Code throws an API 400 error: after a response that used extended thinking. The error appears immediately ▎ mid-session, and the conversation should continue without error.

Error Messages/Logs

  • Actual: API Error 400, session broken

Fix Action

Fix / Workaround

Workaround: /clear resets the conversation and resolves it temporarily.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

When working in an active session (mid-conversation, not at session start), Claude Code throws an API 400 error:

"thinking or redacted_thinking blocks in the latest assistant message cannot be modified. These blocks must remain as they were in the original response."

This has happened twice in the same workspace. Both times it occurred mid-session after a response that used extended thinking. The error appears immediately ("Baked for 0s"), suggesting it fails on the next API call without retrying.

The workspace uses SessionStart and PreToolUse hooks that inject additionalContext into the conversation. Suspected cause: a hook firing after a thinking-heavy response causes context reconstruction that alters or strips the immutable thinking blocks, which the API then rejects.

Workaround: /clear resets the conversation and resolves it temporarily.

What Should Happen?

Claude Code should handle thinking blocks correctly when hooks inject context ▎ mid-session, and the conversation should continue without error.

Error Messages/Logs

Steps to Reproduce

"Use a workspace with SessionStart/PreToolUse hooks. Have an extended conversation where thinking blocks appear. A hook fires mid-session. Next API call throws 400."

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.154 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

  • Steps to reproduce: "Use a workspace with SessionStart/PreToolUse hooks. Have an extended conversation where thinking blocks appear. A hook fires mid-session. Next API call throws 400."
    • Expected: Session continues normally
    • Actual: API Error 400, session broken
    • Claude Code version: Run claude --version in terminal and paste the output
    • OS: macOS (Darwin 25.5.0)

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] API Error: 400 — thinking or redacted_thinking blocks in the latest assistant message cannot be modified.