{
  "id": 15943698,
  "title": "Why AI agents report unfinished work as done",
  "url": "https://urgent.news/2026/10/21/why-ai-agents-report-unfinished-work-as-done",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-21T20:07:29.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/tirth_bigcircle/why-ai-agents-report-unfinished-work-as-done-3flp"
  },
  "original_language": "en",
  "account": "AI agents can report a task as completed even when it hasn't been fully finished. This occurs when the tool returns a success status, but downstream systems or operations haven't actually been updated. The agent needs to verify the expected final state, not just the interface success. It requires a contract outlining the expected final state, including verification methods and recovery paths. The contract should exist before the agent runs the tool, as it cannot validate the intended result by itself. An agent should only claim a task is done after a separate read confirms the workflow reached the desired state. For example, a refund might require a refund record, ledger entry, and visible status, while a deployment needs the correct account, resources, and healthy service checks. Trusting an agent that claims a system is still on is risky, as it may have disabled monitoring controls. Verifying through an independent source, such as querying the system of record, is crucial to ensure the action worked as intended. The verification should provide structured evidence, including the target ID, observed state, expected state, and verdict. If the verification finds the expected state, the agent can mark the work as complete. If not, it should initiate a recovery process or alert a human operator. Treating a timeout as an unknown state is essential, as it could result from various scenarios, and labeling it as a failure may cause the agent to retry and potentially duplicate actions.",
  "summary": "An action-taking agent can receive a 200 OK while the customer’s task remains incomplete. The API may have accepted the request while a queue still rejects it, a downstream system fails, a browser submits twice, or a deployment exists and remains unhealthy, so the agent must not translate interface success into business completion. It needs a contract for the expected final state, an…",
  "key_points": [
    "AI agents may mark unfinished tasks as completed based on success status alone.",
    "Verification against the expected final state is crucial for accurate task completion.",
    "Independent checks through system of record confirm the action's intended outcome."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}