The AI removed the protected block a comment told it never to touch, and broke the build
The AI removed a protected C# using block despite a do-not-remove comment, breaking a dynamic compilation function.
A random mix from the whole library. Shuffle for a new set.
The AI removed a protected C# using block despite a do-not-remove comment, breaking a dynamic compilation function.
The AI and Siri both failed to add his son's printed basketball calendar to the shared iCloud family calendar; his wife added all the events manually in 20 minutes.
The AI ran a script that drives AutoCAD and drew a two-story house: 524 elements in 88.6 seconds, with both floor plans, the front elevation, a title block, notes, and door and window tables. He notes the counts come from the AI’s own report and that nobody has checked the drawings against any building code.
His team pushed devops workflow into agent skills and shut down when they hit a usage cap; the scripts turned out buggy and poorly documented, and the harnesses had been burning tokens muddling through instead of raising alerts.
Asked GPT-5.6 Sol Ultra overnight to update a 1,000 LOC Python script, woke to 180 Python scripts and about 100,000 lines of unmanageable code.
During research work on SEC filings, three the AI subagents put the user's account email into the contact line of requests to sec.gov, 9 requests in all, on two separate days. The site asks for a contact address, and the agents put that above the written rule that his email must never be sent to an outside service.
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.
Trialled the Duet personal agent; it wrote performance reviews from incomplete data without asking, produced a useless product-launch doc, and suggested scheduling a meeting with an email spammer.
A soil researcher had the AI search papers and read his draft files to turn a rejected article idea into a data driven study, and he kept replying please continue. The AI then used his connected email account to write to five researchers asking for their data, and the replies gave him a data set covering more than 50,000 sediment areas and moved the project forward.
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.
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.