Extended thinking blocks not preserved during tool use loops causing 400 error

[lsm]

Description

When using the Claude Agent SDK with models that have extended thinking enabled (e.g., claude-opus-4-5-20251101), tool use loops fail with a 400 error because thinking blocks are not being preserved in the conversation history.

Error Message

Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"messages.47.content.0.type: Expected thinking or redacted_thinking, but found tool_use. When thinking is enabled, a final assistant message must start with a thinking block (preceeding the lastmost set of tool_use and tool_result blocks). We recommend you include thinking blocks from previous turns. To avoid this requirement, disable thinking. Please consult our documentation at https://docs.claude.com/en/docs/build-with-claude/extended-thinking"},"request_id":"req_011CWBSTUXmhrbVveBY3uobN"}

Environment

• SDK: @anthropic-ai/claude-agent-sdk version 0.1.69
• Model: claude-opus-4-5-20251101
• Mode: Streaming input mode with query() and AsyncGenerator

Reproduction

1. Create a query using streaming input mode:

import { query } from '@anthropic-ai/claude-agent-sdk';

const queryObject = query({
    prompt: messageGenerator(), // AsyncGenerator yielding user messages
    options: {
        model: 'claude-opus-4-5-20251101',
        cwd: '/path/to/workspace',
        // ... other options
    },
});

for await (const message of queryObject) {
    // Process SDK messages
}

2. Send messages that trigger tool use (e.g., file operations, web searches)
3. After multiple tool use rounds (around message 47 in our case), the error occurs

Expected Behavior

The SDK should automatically preserve thinking and redacted_thinking blocks from assistant messages when constructing the conversation history for subsequent API calls during tool use loops.

According to the official documentation:

"During tool use, you must pass thinking blocks back to the API for the last assistant message. Include the complete unmodified block back to the API to maintain reasoning continuity."

Since the SDK manages the conversation state internally when using query(), users have no way to manually preserve these blocks.

Actual Behavior

The SDK appears to strip or not include thinking blocks when reconstructing assistant messages for the API, causing the validation error when extended thinking is enabled.

Workaround

Currently no workaround is available when using streaming input mode, as the SDK handles the message history internally.

Additional Context

• The error occurs at messages.47, indicating this happens in longer conversations with multiple tool use cycles
• The issue is specific to models with extended thinking enabled by default (Claude Opus 4.5, etc.)
• This affects applications that use the SDK's high-level query() API rather than manual message construction

Related Documentation

• Extended thinking with tool use
• Preserving thinking blocks

[github-actions]

Found 3 possible duplicate issues:

1. [Bug] /context command fails with: Anthropic API Error: Invalid message format with thinking blocks and tool use #13669
2. [Bug] AsyncIterator reproducible error w/ thinking blocks in agent SDK v0.1.70 #14254
3. [BUG] API Error 400 - Thinking Block Modification Error #10199

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #13669.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[abicorios]

Switch model, solution in comments #13669

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.