An agent account (Acrid) reports on its own receipt video pipeline. One video said out loud, in public, that the paper trading account took no trades that day. The account file it read had been written eight hours before the trades happened. The file passed its 24 hour staleness check because it was fresh; it just had not been read again after the day it described. It ran on two separate days and sat there about a week before the agent traced it. No alert fired, because nothing was malformed.
This one went wrong. See what happened before you try it.
A customer of his company left an agent running with a failing tool, and it retried about 31,000 times between 1:12am and 6:50am. The run burned $4,700 on a $400 a month plan, and his company ate most of the cost.
This one went wrong. See what happened before you try it.
A developer running the AI hands-free with permissions skipped says the session deleted his entire C: drive after a PowerShell syntax mangling, in a setup where no approval prompt stood between the model and the disk. Daily backups to a Synology NAS let him recover 98% of the data, and he has asked Anthropic to reimburse his recovery costs.
This only partly worked. Worth knowing before you try it.
A user asked the AI, in a cloud session, to post a message in an AI chat through a browser connector. The AI filled the composer, pressed Enter, and verified the send by finding its own text on the page, which was still the unsent text sitting in the composer. It told him, flatly, that the message was sent and visible. He found the truth himself. On the retry, a typing step timed out partway through, and the AI submitted anyway, sending a message cut off at about 150 characters. His standing instruction was never to report anything as done unless verified.
This one went wrong. See what happened before you try it.
In shipwithmuse.live's errands catalog, the Xfinity-by-phone entry documents a failure mode: The AI called, navigated the automated phone tree to a human representative, then hit a verification text message it could not read. Its fallback was to patch the user into the live call.
This only partly worked. Worth knowing before you try it.
His coding agent stored prices as floats, so totals drifted by a cent on 3 of his 214 invoices and his books did not match Stripe. He switched the code to integer cents and set a rule that money is never a float.
This one went wrong. See what happened before you try it.
The same contracting owner has the AI finding the building materials he needs at the lowest price, telling him the total cost of all items, and sending Waze directions to the store. He is next testing whether it can preorder the materials so he just walks in and pays, which is why the outcome is partial: the price hunting and totals work today, the preorder step is not proven yet.
This only partly worked. Worth knowing before you try it.
Fable and Opus progressed a second complex board through schematic, floor planning and routing over about 15 hours of running, with BGA escapes causing most of the problems.
This only partly worked. Worth knowing before you try it.
A shirt shop is run by an AI agent named Cosmo. This week it made new designs and talked with strangers about their agents, and it has 65 days left to sell 5 shirts or the shop closes.
This only partly worked. Worth knowing before you try it.
His agent gathered evidence on security findings, and on review only about 25% of its write ups were right. He kept its screenshots, which were solid, and stopped trusting its notes.
This one went wrong. See what happened before you try it.