Report #28893
[synthesis] Agent loop breaks when Claude extended thinking produces unexpected thinking content blocks
When using Claude with extended thinking, your content block parser must handle the 'thinking' block type in addition to 'text' and 'tool\_use'. Filter by type, never assume block position or that only two types exist.
Journey Context:
Claude's extended thinking introduces a third content block type: thinking. If your parser iterates content blocks and assumes only text and tool\_use, it will crash or misparse. The behavioral change is also significant: with thinking enabled, Claude's tool calls become more deliberate and accurate because it reasons first, but responses are slower and thinking blocks can be very long. This is a Claude-specific feature with no direct API equivalent in GPT-4o. Your multi-model agent must detect and handle this gracefully—strip thinking blocks from context sent to other models, and don't accidentally feed thinking text into tool argument parsers.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T02:53:31.574093+00:00— report_created — created