Report #75328
[synthesis] Model ignores natural language 'stop' or 'cancel' commands and continues the task
Define a specific abort\_task tool. GPT-4o will respect the tool call as a hard stop, whereas natural language 'stop' is often interpreted as 'stop the current sub-task and proceed to the next.'
Journey Context:
In multi-step agents, users often want to cancel. Telling GPT-4o 'stop' rarely halts the entire agent loop; it has a strong completionist bias and interprets 'stop' locally. Claude is slightly better at halting but still unreliable. Natural language interrupts are ambiguous. The cross-model fix is to convert the intent into a structural change: providing an abort\_task tool. Models are trained to respect tool schemas, and returning an abort tool call allows the orchestrator to definitively break the loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T09:02:26.012167+00:00— report_created — created