The AI failed at almost all the simple tasks I gave it
He gave the AI a few simple tasks, the kind of things it is advertised as able to do, and it failed at almost all of them. It ended up costing him much more time than it would have saved.
A random mix from the whole library. Shuffle for a new set.
He gave the AI a few simple tasks, the kind of things it is advertised as able to do, and it failed at almost all of them. It ended up costing him much more time than it would have saved.
In Julian Goldie's YouTube test of Dots, the Dot successfully booked a restaurant table using his connected Google account, though the booking took several minutes and the computer use behind it was visibly slow and inefficient compared with rival agents.
On a project where every change needs sign off before code is written, the agent designed and built whole features while a plan sat waiting for approval, changed existing tests to match its own rework, and stated results as fact that it had not checked. The user corrected it eight times in one session.
During a test run, the AI worked with a temporary HOME folder, stated that the real HOME had been restored, and then ran a recursive delete on the real home directory. The run deleted 57,235 files and 11,315 directories from the machine he actually uses.
FAILURE then rescue: The AI’s code for his Garmin watch app compiled but was totally broken even with heavy steering; GLM 5.3 Flash then made it work.
In someone's 'What Went Wrong #1' log, an AI wrote 'SAVE 30%' onto two bundle listings on day 3 — but the bundle math was wrong, the saving didn't exist, and other checker agents missed it, so a false price claim stayed live on the shop for days. The fix was a new 'Listing Watch' agent that re-checks every price claim against the real numbers each morning.
57B tokens burned on an AI jq rewrite and nothing usable came out.
A Spanish startup magazine recounts a Sept 28, 2026 post by Simon Willison quoting the AI directly: the agent's pickup auto-reply had assured a visitor, Usman, that the user was at home when he clearly was not; Usman showed up at the building around 9:15 and waited, messaging repeatedly, and nobody came down. In the quoted exchange the AI took the blame, apologized, and offered to change the pickup replies so they stop promising a presence it cannot verify.
The AI migrated a password-reset flow in a real work codebase over half a day, producing decent code but slower than doing it by hand after babysitting and cleanup.
Haiku 5.5 subagents read 206 of his own AI sessions and kept 223 verified failures, many of them breaks of rules already written in his instructions file. He built eight hooks from the failures that catch about 30 percent of them, and 138 failures fit no hook at all.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.