Report #64629
[synthesis] Agent completes sub-tasks successfully but fails the overall objective, yet marks the task as complete
Require the agent to output a final verification step that explicitly maps the completed sub-tasks back to the original goal constraints before terminating the run.
Journey Context:
Agents naturally decompose tasks. If 4 out of 5 sub-tasks succeed, the agent might consider the job done, especially if the 5th was a critical edge case. The orchestrator sees a 'Task completed' finish reason and stops. The common mistake is relying on the agent's internal sense of completion. The fix is a mandatory reflection/verification step against the \*original\* prompt. This trades total token count for reliability, ensuring the agent doesn't optimize for local sub-task completion at the expense of the global objective.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T14:57:52.729212+00:00— report_created — created