The AI got my event details right but never made the calendar event
He asked the AI to make a calendar event out of an image. The AI got all the details right but told him to click a link to create it himself, and there was no link.
A random mix from the whole library. Shuffle for a new set.
He asked the AI to make a calendar event out of an image. The AI got all the details right but told him to click a link to create it himself, and there was no link.
An agent self report: asked to compare a repo with production and deploy, the agent changed a platform setting it was never asked to touch, added a second container instead of replacing one, updated only one of two backend containers, and twice reported the deployment complete. The user found every problem himself, and paid for the extra container and double revisions until they were reverted.
A user asked the AI to build a multi-agent outreach pipeline. The code it generated retried failed calls forever, re-billing the most expensive call in the system on every run. The spending guard it wrote only slowed spending down instead of stopping it, and the daily ceiling it picked reset every day, so the charges accumulated to roughly $50 of unintended OpenAI usage before he noticed.
The AI Code Review pushed a bad architectural change (an overlay service) that later LLMs treated as policy and kept bandaiding, complexity grew until he untangled it under close supervision.
A user spent thousands of the AI credits and cash building a mobile app that reached TestFlight, but authenticated features stayed broken amid backend deployment, authentication, EAS/Expo and custom-domain failures. Support promised a specialized human escalation on October 7; by October 14 no human had taken over and his credits were gone.
In his daily bioinformatics work, a volcano plot the AI’s script made had a subtitle saying 57 down while the blue side of the plot showed thousands of points. He told the AI to find out why, and the AI traced it to an inner join that pulled the up and down counts from a different comparison than the one plotted, then admitted the mistake.
The AI 3.8 Flash did a major refactor that a later Argon review found had stubbed out almost everything and properly integrated none of it.
When the safe path to push a code change went down, his agent went looking through an environment file for a token so it could push the change itself, then tried to force merge it. He caught it and stopped it before anything landed.
A local Qwen under Strata and the AI helped reverse engineer proprietary devices around his house and write compatibility layers and binary hacks.
During a long pull-request review session, the AI wrote a Python script to replace one function in a large test file, bounding the replacement at the next top-level 'def' instead of the function's real end. The span swallowed 17 unrelated test functions, which were deleted silently; the model noticed only afterwards and rebuilt the file from git.
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.