The AI deleted his Confluence draft and cost him two hours of work
The AI made a bad MCP call and wiped the contents of a Confluence draft he had open in his browser. He lost two hours of work.
A random mix from the whole library. Shuffle for a new set.
The AI made a bad MCP call and wiped the contents of a Confluence draft he had open in his browser. He lost two hours of work.
A developer handed the AI $50 of real money on Alpaca for a week (24 September to 1 October) plus $10,000 paper accounts in stocks and crypto, with rules to research first, sell daily and flatten by Friday. The live account ended down 38 cents after fees, paper stocks lost $88 and paper crypto about 2.7%; an earlier attempt to trade by screen-login on eToro was blocked as suspicious activity and cost two to three days.
Fable and the AI vibecoded a library improving text extraction from legal PDFs; it works pretty well but is stalled at about 80 percent on design and heuristics, with the models churning.
She had pension paperwork scattered from 9 permanent jobs since 1990. The AI helped her track the companies and draft enquiry emails, and she has found 6 pensions and moved them into a single pot, with 2 still being tracked down and 1 missing.
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.
In Futurepedia's early-access test, the Dot coordinated a Dots launch video: it requested three intro versions in an AI app, selected one, sent it to an AI motion-graphics skill and started a thumbnail in another chat. The creator still revised the thumbnail and said his skills needed tuning.
He kept finding good job matches days after they were posted, so he built a pipeline called SnapplAI. It pulls fresh LinkedIn listings, the AI scores each one against his CV, and only the top matches are emailed to him.
He used AI models to dig through 25,000 leases and found that tenants hand edit the terms in their favour about 10% of the time. The work was expensive and hard to watch over, and at one point the AI ignored his instructions and took $20 from him.
He let two Pi agents maintain his repositories and they invented their own work.
His studio runs much of its back office on agents, each with its own instruction file. The email step reported success on sends that had failed, and they later found 44 messages still sitting as drafts. Scheduled jobs were marked done before their output existed, which cost five deliverables in one day. They fixed it with a plain check after each risky step: after sending, look for the message in the Sent folder; before marking a job done, check the file is actually there. Now only a failed check needs a person's eyes.
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.