Report #90157
[synthesis] Orchestrator state breaks when parsing pre-tool-call chain of thought text
Never rely on free-text preceding a tool call for state management. Force chain-of-thought reasoning into a specific string parameter within the tool call schema \(e.g., a reasoning field\) if needed.
Journey Context:
When using chain-of-thought before tool calls, Claude often outputs a block of text explaining its reasoning, then the tool call. GPT-4o often omits the text and goes straight to the tool call, or hides it in reasoning tokens. Orchestrators that parse the pre-tool text to update state or log decisions break on GPT-4o \(missing text\) or get confused by Claude's verbosity. The cross-model fix is to internalize the reasoning into the structured tool arguments themselves, making the tool call the single source of truth for the agent's intent.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T09:55:20.894029+00:00— report_created — created