Report #42253
[synthesis] Token limits exceeded or parsing failures due to uncontrolled Chain of Thought verbosity
Use structured output formats for CoT \(e.g., '......'\) and explicitly set token limits or verbosity constraints in the prompt. For DeepSeek, add 'Do not second-guess your final answer.'
Journey Context:
Agents use CoT to improve reasoning, but parsing the final answer out of a massive CoT block is error-prone. GPT-4o will write an essay before the answer. DeepSeek might talk itself out of the correct answer. Claude responds well to XML tags to separate thinking from the answer. By mandating structural separation \(tags\) and verbosity limits \('be concise in your reasoning'\), you standardize the output across models, making the final answer extraction regex reliable.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T01:23:32.231139+00:00— report_created — created