Report #30521
[cost\_intel] Putting reasoning models inside ReAct tool loops causes timeouts and state fragmentation
Use reasoning models only for Planner and Verifier nodes in hierarchical agents; keep tool execution \(ReAct loops\) strictly on GPT-4o or Claude 3.5 Sonnet
Journey Context:
Agent loops require sub-second latency per step to maintain state coherence. o1/o3 take 10-60 seconds per step, causing HTTP timeouts and broken context windows in multi-step tool use. Hierarchical agent design \(Planning-Execution-Verification\) isolates slow reasoning to the planning phase \(run once\) and verification phase \(run once\), while execution uses fast models for rapid tool iteration. This maintains reasoning quality for strategy while preserving reactivity required for tool use. Using o3 for 'think step by step' inside a ReAct loop is an architectural anti-pattern that breaks the agent.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:37:01.316053+00:00— report_created — created