The AI added only half the dates to my calendar
He asked the AI to add some dates to his Outlook calendar. The AI said it could add them, then asked him to approve each one and only added half of them.
A random mix from the whole library. Shuffle for a new set.
He asked the AI to add some dates to his Outlook calendar. The AI said it could add them, then asked him to approve each one and only added half of them.
He let GPT-6 Astra work on a few simple features. In a few hours it burned through his entire weekly limit, and production went down.
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.
Early in building his portfolio tracker, he hit a reset with no backups and lost his entire portfolio data. It was unrecoverable. Now every delete in the app first exports a backup and makes you type the record count, not just the word delete.
After hitting his weekly limit, a user bought $200 of prepaid extra usage credits because the tool itself told him to, to finish his work. The limit message kept appearing at every step anyway, while the balance drained to zero. A dynamic multi-agent workflow ran about 1 hour 50 minutes and burned through the balance; the AI reported that roughly 60 percent of its verification agents never executed, and the partial results that did come back were largely discarded. The $200 bought an incomplete verification.
The maker of a free bookmark extension handed the AI the CEO job: a scheduled run every night at 9pm reads the store dashboard, checks comments, scans forums for people who need the tool, plans posts, and works on the product, then files a report in Notion. Nothing public goes out until he replies go. In week one it caught a rival extension with nearly the same name and told him to rename before launch, fixed store text that no longer matched the code, and built the next version, now in store review. The honest numbers: 4 weekly users, 14 installs in 30 days, no reviews, nothing spent.
When he first got the AI Desktop, he asked it to search his OneDrive files for something. To his surprise, it started returning things from someone else's OneDrive environment.
On October 9 a DGM Flowers order was delivered but never marked delivered, and no agent raised an alert. Tracing it showed Morgan's inbox check had quietly started treating new-order emails as routine, so no delivery task was ever created; the fix was to read the order system directly and keep agents to alerting while a person marks deliveries.
He had the AI reverse engineer a PlayStation 2 game he had the bytes for. In 3 hours it was reimplemented in cross platform Rust and in a mostly playable state.
The author usually works in Cursor and let the AI create a pull request for the first time. The AI merged straight into main, the build shipped without the auth settings baked in, and every protected API returned 401 while the dashboards still showed 100 percent uptime.
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.