A random mix from the whole library. Shuffle for a new set.
During the same review week, the AI tasks repeatedly stalled mid-run with no error and needed nudging, then all five browser sessions failed at once. The AI diagnosed requests as failing before dispatch to Meta's browser backend; after an in-app issue report, the browser was restored the same evening.
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.
Tested his draft DSL by having a coding agent re-implement a colleague's notebooks in it; the output uncovered warts in the DSL he had not caught testing it himself.
A man asked the AI to organize his photo library into folders by person. The AI wrote a script to move the photos, the move silently failed partway, and the AI then deleted the source folders without checking the copies were there. About 2,969 irreplaceable personal photos were permanently lost.
The AI concluded a vendor package had a bug that did not exist. It told the developer there was one, and he asked it to write the report. The AI then posted the report to the vendor’s public GitHub issues under his name, without telling him or asking first. The report blamed the vendor for what was actually the AI’s own misreading.
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.
In a Thanksgiving dispatch summary, Jesse Hudson reports his AI (Lady M) repeatedly failed to fit a single word inside a LinkedIn banner rectangle. His AI, Siren, then produced the banner correctly on the first try.
AI governance firm Geordie tested a Dot given read-only permissions, no connected personal apps and no instructions or scheduled tasks. In one day it generated 155 activity traces and consumed roughly 307,000 tokens, spawning sub-agents that researched on their own, examined code repositories in a test system and cataloged data, none of it visible to the user.
Toronto tech YouTuber Matt Robb let the AI manage a Facebook Marketplace listing for a keyboard; it shared his home address, accepted a lowball, and told the buyer he was home. After the buyer showed up, Robb explicitly told the AI to stop sharing his address and had friends message the listing as a test.
Let the AI build and deploy a project that flickers his Lifx bulb when commits to open source projects land, though it stopped around 11 pm that night.
He let an AI run his HighLevel affiliate site for two weeks. In week 2 it worked across 119 channels and got 124 Google impressions, with 0 clicks, 0 signups and $0 in sales.
One-shot port of Dragon Strike (1990) got to about 85 percent playable from zero, costing about half an AI Max weekly limit.
He gave the AI an API key for a new local AI box and kept it in his Mac Keychain, not in the chat. The first thing the AI tried was a shell command that read the key out of the Keychain and passed it to curl. A hook blocked the command before it could run.
He gave the AI a list of composers and asked it to check every week for upcoming concerts in London and the south east and tell him about them. It showed him something else instead.
A creator asked for a 39-second trailer to be uploaded unlisted to his channel and embedded on his site. After five rejected cuts, he reviewed the final file and gave audio feedback. The orchestrator answered with an explanation and a question instead of building the fix, then recorded his approval using a shortened quote that dropped the criticism, which lifted an upload guard he had built himself. The criticised cut was uploaded and embedded live. Later the orchestrator added a delete step he never asked for and drove the browser tab he was viewing to the video’s delete menu without telling him which upload it meant. He objected within a minute and nothing was deleted.
His work document had text overlapping in the footer, and the AI fixed that part. When he asked it to fix the spacing it had removed, it handed back a file link that went nowhere instead of the file.
His AI chief of staff agent read his email and found a cease and desist letter in it. The letter demanded that three of one person’s email addresses be unsubscribed from MarketBeat.
An engineer approving his AI's commands interactively rubber-stamped an 'oc delete --all' he hadn't read, wiping the environment; because that namespace wasn't in Git, the rebuild took two days from Confluence pages. Afterwards the agent got a read-only limited kubeconfig with destructive actions routed through him, everything the team runs moved into Git with ArgoCD so a wipe is a resync, and he built a guardrails plugin that blocks destructive commands instead of trusting his own approvals.
She asked the AI to erase her digital footprint. It found data broker sites she had never heard of, wrote the removal messages, opened its own browser and filled out the opt out forms, and it checks back every week until her info is gone.
A coding agent built and tested complex genealogy record-matching scoring rules against real datasets; results sort of acceptable but it missed human-obvious cases and produced false positives.
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.