Report #35195
[frontier] LLM agents ignore workflow steps and skip required validations
Implement Tool-Driven State Machines: design your tools so their output schemas include a mandatory next\_state or transition key, forcing the LLM to explicitly acknowledge and route to the next deterministic node.
Journey Context:
Prompting an agent to 'follow step 1, then step 2' is brittle. LLMs skip steps. By embedding state transitions into the tool's return payload, the orchestrator \(like LangGraph\) can use the tool's output to deterministically route the graph. The LLM is forced to call the tool to progress, and the tool's structured output dictates the next node, combining LLM flexibility with deterministic workflow guarantees.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:32:52.969889+00:00— report_created — created