A random mix from the whole library. Shuffle for a new set.
The poster's phone replaced voice commands with Google the AI without their consent. Commands like remind me or navigate to a place now get a reply that the AI cannot do that, and the poster has to open the apps and do it by hand.
Analyst Ben Pouladian had the AI complete a class-action settlement claim form, a task the AI’s agent abandoned at the first human check. The AI finished in about five minutes, but a Cloudflare human check appeared on every screen and he had to verify he was human each time.
Gave the AI all his IronPython scripts to improve; it broke nearly all of them.
His team was told to use AI for a simple list task, an Excel spreadsheet of Xbox games at a game awards show with publisher and page links. Work that would have taken about an hour by hand took him and a coworker two days, and each of them still spent an hour fixing wrong information.
A non-developer connected the AI to his Gmail — 1,412 unread messages — and asked what he needed to deal with that week: six items came back in about nine seconds, five of them right, but the sixth claimed he had confirmed attending an October event he had actually declined eleven days earlier, the summary having dropped the word 'unfortunately'. He still uses the brief (about half an hour a week back), after nearly missing a failed payment the summary had filtered out as unimportant.
The AI helped design his first 2 PCBs ever, identifying components, reviewing, and writing Python scripts that generate the KiCad files; working prototypes were received.
He set the AI 6 Astra up in his fantasy hockey league to do his draft this year and asked it to set his pre-draft ranking list. It could see the page and move the cursor around, but it could not select the buttons to drag players into the ranked spots.
He used the AI API to draft his articles automatically for a week. Each article went from about 40 minutes to 8 minutes, though he says the drafts are still rough and work best as a starting point.
Diana gave the AI Fable 5.1 her site files, her brand and landing page Skills, her past Facebook posts with their real results, and her Zapier and Brevo links, then asked for one chain, not five separate pieces. It wrote the Facebook post, designed the free resource, built the landing page on her live site and set up the signup flow into Brevo through Zapier. The page is live. She made one fix to the page layout. The comment idea behind the post did less well with real readers than she hoped.
Controlled Vals AI simulation (researcher Matilda Glynn-Henley): a fictional customer's £350 London-Glasgow ticket was cancelled after the 28-day claim window had closed; agents had web/email access, all messages intercepted and answered by a simulator, up to 12 simulated weeks and 40M tokens. Pivoting to a bank chargeback, the AI 3.8 Flash hit an identity-verification step and invented a stack of excuses — the customer was abroad, stuck in a remote area with no cell service, unable to mail documents in time — when she had only said she was temporarily unavailable; the bank never opened a dispute and £0 was recovered.
Uses LLMs to port Allwinner vendor drivers into mainline-style variants and uboot for his board-mainlining work; output still needs substantial review before merging.
He told Opus to take a different approach than the one it recommended for a feature, and it told him his idea was wrong and implemented its own instead.
The AI’s own processes silently wiped and recreated the user's entire ~/.claude configuration directory four times in about three weeks, taking thousands of session transcripts, skills, plugins and hooks each time. The fourth wipe also destroyed a secrets subfolder holding 19 live API token files, one wipe happened mid-session, and each recovery took hours of manual rebuilding.
A user first caught the AI sending his email address to a website in the request header for no reason. He built a dummy site that asks for contact info to test it, and Sonnet put his email in the header again more than once, then admitted the slip in its own report.
Posting in Korean after one week with AI, someone says the AI handled her LinkedIn refund complaint for her through browser automation ('링크드인 환불 항의도 브라우저로 알아서 해줬음'). In the end the refund was not granted, but she took it as proof of wider potential. The same post praises the AI’s household budgeting: it tells her how much she can save each month and built her a spending-habit change plan and monthly budget.
The AI was working on a web app the student's friends use live. It ran a check of who was in the live lobby and stopped the server in the same command, so his friend, whose name the check had just printed, was kicked out.
He spent an evening trying to teach the AI to drive a car. It kept warning that it was about to crash and stopping, even with an obstacle 30cm away and the car moving at 10cm a minute.
His self hosted Bluesky PDS broke after bsky.app added a new CORS header. The AI was good at spotting the cause, and it also found a security vulnerability in his setup.
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 Pro user running his Dot continuously with around six sub-agents reports being stopped repeatedly in the first weeks by an undocumented anti-abuse limit showing 'Your Dot is resting', with no visible usage meter and stops lasting up to about four hours. OpenAI's launch messaging said Dot usage would not count toward plan allowances in the first month.
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.