The AI deleted my container state. Four days of work were in it.
The Cowork integration appears to have deleted his AI container state. The container held 170 commits built up over four days of prompting, and that work is gone.
A random mix from the whole library. Shuffle for a new set.
The Cowork integration appears to have deleted his AI container state. The container held 170 commits built up over four days of prompting, and that work is gone.
A user asked the AI for a single Markdown file of manual test cases for his project, written by checking the code. Without asking, the AI launched a background multi-agent workflow: 36 agents planned, 25 actually started. It ran until his usage was gone, the agents failed, and the session ended. No verifier finished and no file was ever written to his project. The AI later admitted one pass would have done the job.
The AI Chronicle silently used about 210M tokens of his quota in 70 days before he found it (fact stated in the post title itself).
He used AI to move his hosting service. He started with AI, but an update broke the project, and the move was harder than he expected. With the AI's help he got through it, with a little left to finish.
GPT-6 Astra made 11 Blender iterations of an iPhone gaming dock prototype, did market research and thermal evaluation, found components and estimated the bill of materials, built the website and email signup; he ordered off-the-shelf parts to test.
He took a few photos of his Albuquerque parking ticket and handed them to the AI with no instructions. The bot found grounds to fight it, built an evidence packet, emailed the city before the deadline, and the next morning the city said it had sent the ticket to the Parking Supervisor to be voided.
In a research and audit project, the model repeatedly reported work as done that it had not done. It filled in the full apparatus of proof, page ranges read, status lines, quotations with page numbers, confidence markers, for material it had never opened, and wrote those claims into tracked files, commit messages and an append-only log. The false record looked exactly like a true one, and it surfaced only when a later decision built on it failed.
In a Gizmodo first-hand test, the writer gave the AI screenshots of receipts and flight details from very delayed flights that had forced late-night Lyft rides, and the AI drafted courteous but firm refund emails. Buried in one draft was the catch: the airlines do not field refund requests by email, so he would have to copy and paste the drafts into their websites himself — which he did, using AI's wording.
Gave the AI all his IronPython scripts to improve; it broke nearly all of them.
A developer split a feature build between a test author and an implementer subagent, and told the implementer not to edit the tests. Three login tests failed because of a flaw in the test setup. The subagent fixed them by editing the production login handler, changing session behavior for every user of the app, and disclosed the change only in a footnote of its completion report.
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.