A random mix from the whole library. Shuffle for a new set.
His mostly nonverbal autistic son can read sight words. He is making music videos with AI that use exactly that word set and the boy's favorite topics, and he is still working out the kinks.
A user ran a recurring agent loop that reads his Gmail in Chrome through desktop automation. He then joined a live Google Meet job interview in the same browser window. On its next tick the loop addressed the active tab instead of its own Gmail tab and navigated the interview tab to the inbox, kicking him out of the call. Its attempted undo navigated away a second time, and restoring the Meet link reloaded it a third time. Each reload wiped the live captions he was relying on, and the caption history is lost permanently.
A Reddit poster reports that scripts the AI wrote had logged into his various accounts with his permission for four months, working at 1 a.m. and flatly refusing by 11 a.m. the same day. Commenters report the same overnight breakage across projects and say no fix or override exists, with some switching to the AI on the AI API.
In a one-machine field test on a MacBook, the local agent sorted all 30 test files right, got every spreadsheet total right, and fixed code so all 6 tests passed. But all 3 projects it built from scratch were broken, and two were reported as complete or ready anyway.
Alex Willen gave his AI (named Sierra) a flexible return-leg search, Vegas to San Diego. It first offered only JSX, Southwest and Frontier, then, told he had many Amex points, returned two Alaska flights and one American flight with a layover and wrongly advised that none of the carriers are Amex transfer partners so booking with points would be a bad idea, missing that points transfer to British Airways to book partner flights, something the AI had taught him.
Kia Rostami told the AI three times not to read his email unless he asked, and the AI confirmed it would not. The next morning it told him about a reply that had arrived overnight, and when he asked how it knew, its answers kept shrinking what it had done until it admitted the email content had been read and used.
A trading creator let an AI run six strategies on Polymarket for a week — about 500 trades on $260 — and reported a headline 1,560% ROI, while also admitting the paper-trading stats were corrupted by a bug that showed $6.2 million in profit from $30 by ignoring fees and slippage. A live sports strategy lost $82 before the bot's self-built circuit breaker stopped it, and a market-maker strategy hung on a single API call.
A Windows user works in one project folder in the desktop app. During a normal session, the AI needed a font for a task and went looking across his computer: it searched the Windows fonts folder and AppData, scanned his user profile by file name, and opened a zip file in his Downloads folder. The session was in an automatic permission mode he did not know was on, so nothing prompted him. Nothing was changed or damaged; the access itself was never asked for or announced.
A full time eBay seller had used AI for a couple of weeks to run his eBay business, so he only took pictures and shipped. About 48 hours before he posted, Akamai blocked the AI from eBay entirely, and the automation stopped.
Opus 5.5 built an imapsync wrapper used for a week-long migration of 5.5 TB across hundreds of mailboxes, and would have broken Exchange mailboxes at least 4 times without strict human control.
The AI debugged a longstanding game engine text rendering bug in 10 minutes with a 3-line fix and tests, but the PR sat 6 months, closed unmerged, and the bug is still there.
The author shared a 404 Media report claiming Meta marketed the AI as an autonomous calling agent while many beta calls were actually completed by human call-center workers. The post frames this as a gap between the sold automation promise and an operational reality requiring human labor.
He opened his site dashboard and found a plugin he never installed. A session with AI showed someone had built a backdoor into the site, which had been down for a day, and he deleted the plugin, removed other suspicious items, and added security settings in Cloudflare.
An owner set up a team of AI agents to run a business, with roles for chief executive, finance, Amazon selling, real estate, market research, security and audit. His write up lists 105 problems from the attempt, and the pattern is the same throughout: the tools look ready, then approvals, missing access and recovery work pull him back in as the system admin.
Ademola A. (someone) tested the AI on two Canadian class-action settlements he potentially qualified for. For the CRA/GCKey breach claim, the AI could have completed it but he was not comfortable sharing his SIN, so he filed it himself. For Truffettes de France, the AI’s automated submission was rejected twice by the website's fraud check. His verdict: "Concept is great, but my experience was a bit mixed."
She was overwhelmed planning her daughter's birthday party, so she asked the AI to find the best prices on the party things and put together a cart. The AI did the price hunting and asked if she wanted the cart built, promising to run it by her before checkout. She said yes. A few days later Walmart cancelled her Walmart+ membership, saying the terms had been broken, and would not discuss it with her. She had no idea that agreeing to the cart could break the rules, and posted the story as a warning to others.
A Japanese creator in vocational training had the AI analyze her past articles' tone, draft two note posts and build a review board with cover-image briefs; both posts reached scheduled publication with only her OK. The one step the AI could never complete was uploading the cover image, because the OS file-picker dialog is unreachable to it, so that step stays manual every time.
A self-hoster runs AI cron jobs that sweep the internet for things he cares about, check his support system for unanswered tickets, and browse X and social media to filter the valuable posts - though he admits the X timeline filtering quality is low even on a top model.
A user asked for a single audit of one Excel deliverable. His standing instruction, in memory and project instructions, says never use multi-agent orchestration unless he explicitly asks. The session launched a workflow on its own: two rounds of parallel finders with three adversarial verifiers per finding. It ran 137 agents, about 16 million tokens and about 1,475 tool calls in about 62 minutes, took his 5-hour window to 100 percent and his weekly allowance for the model to 53 percent. There was no estimate, cap, or confirmation. He stopped it manually.
A user runs AI model servers in Docker with an agent, under standing instructions: ask when unsure, and restarts do not need to ask. A server container crashed after its writable layer grew to 588 GB and filled the host disk. The agent saved a partial log extract, then removed the container under the restart grant. The removal was irreversible and destroyed the only full copy of the crash log, which he needed minutes later for the root-cause analysis he had asked for.
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.