{
  "id": 155707,
  "title": "I Audited My AI's To-Do List. A Quarter of It Was Already Done.",
  "url": "https://urgent.news/2026/08/05/i-audited-my-ais-to-do-list-a-quarter-of-it-was-already-done",
  "topic": "ai",
  "section": "AI",
  "published": "2026-08-05T02:35:29.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/nickmeinhold/i-audited-my-ais-to-do-list-a-quarter-of-it-was-already-done-1k01"
  },
  "original_language": "en",
  "account": "An audit revealed that a quarter of the open tasks for an AI agent were already completed, despite the system reporting them as \"open.\" This discrepancy arose because the AI system creates tasks automatically when work begins, but closing tasks requires manual bookkeeping after the work is finished. As a result, tasks would remain in the backlog even after completion, leading to inaccurate reporting. The audit confirmed the reality of completed tasks by checking external sources like email, calendar, and git tree, ensuring that only verified completion would be considered \"done.\" This illustrates how systems where the completion signal is separate from the creation signal can produce unreliable self-reporting, and highlights the importance of verifying reality against these reports to maintain accurate task management.",
  "summary": "My coding agent has a to-do list. It lives in a public GitHub repo — one issue per task, labelled by project, opened and closed automatically as the agent works. At the start of every session the still-open issues get read back in, so a backlog survives across sessions and across machines. The agent picks up exactly where the last instance left off. This morning I asked it to reconcile that…",
  "key_points": [
    "AI agent reported 25% of tasks as \"open\" despite completion",
    "Manual bookkeeping required to close tasks after completion",
    "Audit verified task completion via external sources like email"
  ],
  "editors_take": "The audit's findings underscore the need for manual verification in task management systems where automated task creation outpaces completion tracking, to prevent artificially inflated backlogs and ensure reliable reporting.",
  "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."
}