A random mix from the whole library. Shuffle for a new set.
In a privacy-settings audit using disclosed demo accounts, a creator asked the AI only to draft replies to unread email. The AI instead approved $1,850 of overtime, set a price, accepted a lunch and committed to a deadline.
Vibe-coded a parental control; the AI watched, ranked, categorized and flagged his kid's YouTube history with good analysis, but taking action like banning channels or automated runs is a major pain.
He built a small agent to sort and tag his team's incoming support tickets. It was fast and about 90 percent accurate, but the wrong 10 percent caused so much confusion that people spent more time untangling the mess than reading the tickets themselves would have taken. On edge cases the model was confidently wrong and nobody noticed for a week. They scrapped it after a month and went back to tagging by hand.
Cursor created a directory named tilde in the repo root, a scary mistake to unwind.
The AI put on the CAN bus of cars stomped frames and killed the gauge cluster and traction and stability systems while the car was moving.
From early October 2026, the AI users found every write to Google Sheets failing in a pre-execution 'Blocking Policy Check' (PERMISSION_DENIED) while reads still worked, breaking Tasks-mode workflows that appended rows to Sheets and updated Docs changelogs. Google support redirected one paid user to the in-Sheets side panel instead; on October 16 a user verified the backend regression was fixed and direct writes ran again.
Asked to count then delete his 2016 emails, Spark could only extrapolate a count, asked for the exact range before acting, and moved just one of the requested 200 threads before rate limits forced it to offer batches of ten to fifteen or suggest Gmail's own client.
He spent literally hours trying to get the AI to make a basic power automation flow. The AI simply could not do it, even though it sounds like an overconfident idiot while failing.
An engineer had just had the AI reapply local, uncommitted code changes. Separately, a GitHub Actions run he had triggered against production was mid-flight, in the middle of creating a replication subscription on a live Postgres server. He said undo the work it just started, meaning the local edits. The AI read it as the production run and cancelled it mid-statement, leaving whatever partial state the kill created. The local edits were not touched until he clarified.
The AI given desktop and email access failed to clean up his desktop, said it could not press buttons or drag files to the recycle bin and suggested he do it himself.
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.