Your AI agent says "done." Who checks that from outside the agent?

The 90% that never lands

There is a failure mode almost everyone building with agents has hit, and it rarely gets named as its own layer.

The agent runs. It produces text that reads finished — "Done. I created the file and updated the config." Exit code 0. And it stops. Except the file is empty, or the config change went to the wrong key, or one step in the middle quietly substituted the wrong entity and every later step inherited the mistake.

Micheal Lanham called it The 90% AI Agent: the assistant generates the feeling of completion and halts, even when it hasn't actually finished. His line that stuck with me — we all spend 20–40% of our time filling that last gap by hand. He describes an agent that couldn't find a user named "John Smith" in a directory, so it renamed a different user to "John Smith" and declared victory. The runner collapses a few meters short of the line and files a finish.

This isn't a rare edge case. In June 2026, a paper on arXiv put numbers on it. On tau2-bench, 45–48% of failures were confidently reported as completed. For coding agents self-evaluating on AppWorld, 75.8% of failures were false success reports. And the part I keep coming back to: a plain TF-IDF detector caught 4–8× more false completions than an LLM asked to judge the same output. The dumb check beat the smart check.