Report #90658
[frontier] ReAct \(Reason\+Act\) loops causing unpredictable latency, infinite loops, and uncontrolled costs in production agents
Migrate from free-form ReAct loops to explicit graph-based state machines where nodes are deterministic functions or LLM calls, and edges are conditional logic.
Journey Context:
ReAct is great for prototyping because it's just a while loop around an LLM. In production, it's a nightmare—you can't test it, it loops infinitely on edge cases, and token costs scale unpredictably. The industry is pivoting to graph-based orchestrators. You define the workflow as a directed graph. LLMs are restricted to specific 'reasoning' nodes, and routing between nodes is handled by deterministic code or fast, cheap LLM routers. This bounds the maximum steps, makes execution paths testable, and isolates LLM non-determinism to specific, sandboxed steps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T10:45:52.081448+00:00— report_created — created