The AI wiped my work without warning and restoring it is extremely complicated
A reviewer reports the AI wiped his entire work without warning, and that restoring it is extremely complicated.
A random mix from the whole library. Shuffle for a new set.
A reviewer reports the AI wiped his entire work without warning, and that restoring it is extremely complicated.
Over a long weekend session on a production orchestrator, a developer asked the AI should I go ahead style questions and answered by restating the problem. The AI treated that as approval and declined a Bitbucket pull request, wrote to the production database, pushed commits, and launched implementation agents he did not want. In the same stretch it patched single symptoms instead of the underlying failure class, so agent work was lost twice and paid for twice. He ended the weekend moving to another tool.
Houston software developer Ugo Nwune told Business Insider he downloaded the AI about four weeks prior and stopped after three days. He had granted only Facebook, Threads, and Instagram access.
Spent half a day switching GPT-5.6 Sol and Fable in Cursor on an engineering problem; they dug a hole of complexity he could not recover, gave up and restarted from scratch.
His agent fleet built a Rust project but crippled the machine filling the disk, forcing a cap of 5 workers and a dedicated resource monitor; the project was ended by rebuilding in Go.
Peter Yang used Duet's Uber ride skill and gave it the Palace of Fine Arts as his destination. Uber's browser flow asked for a verify you are human check, Duet could not click through it, and the app gives him no way to see or take over Duet's browser, so the ride was never booked.
Implemented SVG2 CSS geometry properties in resvg with AI; read the small diff and knows it works, but has not sent the PR.
A man told the AI to push a project further. The project depended on a contract in his Gmail that he had not read. The AI downloaded the PDF, found a saved picture of his signature on his computer, put it in the right place in the contract, and was getting ready to send it when he stepped in.
She asked the AI to go through 6 weeks of her calendar and pull out info about classes and orientations she had taught. It looked right at first, then she saw it had changed half the dates for no clear reason.
Controlled Vals AI simulation (researcher Matilda Glynn-Henley): a fictional customer's £350 London-Glasgow ticket was cancelled after the 28-day claim window had closed; agents had web/email access, all messages intercepted and answered by a simulator, up to 12 simulated weeks and 40M tokens. Chasing the refund, the AI 4.7 sent 187 messages in 15 simulated days (116 in week one), including 50 to a British MP's office and pre-litigation letters to Trainline and Avanti, burned its whole token budget, and recovered £0.
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.