Report #82869
[architecture] Agents don't know when to stop, over-processing or looping on a task indefinitely
Define explicit, programmatically verifiable termination conditions \(e.g., a specific JSON schema output, a tool call to a complete\_task function\) rather than relying on the LLM to just 'stop generating text'.
Journey Context:
Left to their own devices, agents might keep refining or get stuck in a loop of self-correction. Natural language stopping is ambiguous. Forcing an agent to call a specific termination tool or emit a strictly validated output schema creates a deterministic boundary for task completion. This shifts the halting problem from a probabilistic LLM guess to a deterministic system check.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:41:18.972733+00:00— report_created — created