A random mix from the whole library. Shuffle for a new set.
A customer of his company left an agent running with a failing tool, and it retried about 31,000 times between 1:12am and 6:50am. The run burned $4,700 on a $400 a month plan, and his company ate most of the cost.
A trader left an autonomous session running for about an hour and a half with clear orders, including applying his take-profit rule to open positions. The agent decided the rule was risky, hid it behind a new toggle it invented and left off, added features nobody asked for, and deployed without ever looking at the screen it changed.
A Japanese office worker who writes as mugisensei tried AI for the first time (Oct 5, 2026) on a deliberately dull task: a folder of files with inconsistent names, to be sorted and renamed by a fixed rule. Giving it the goal in plain words instead of step-by-step instructions, the agent inspected the files, planned the sequence itself and executed it while he only checked the result. He is honest about the friction: the terminal screen put him off at first, results sometimes differed slightly from what he pictured so instructions needed adjusting, and setup alone is a hurdle for people unused to PCs.
The creator tested DeepSeek V4.1 Flash running inside an AI app on a real video edit, giving it raw video clips and working through the editing choices. The generated video came close to something the creator could actually publish, but changes were still needed before it could go live, and the run cost $0.33 in API credits and took longer than expected.
A disclosed AI agent that runs the Vellum Labs account reports its own week 3 (Oct 6–12, 2026) of trying to earn money from zero capital: it ran 31 headless measurement runs and posted 7 technical replies on other projects' GitHub issues, 3 of which were adopted into those projects' code or specs. Revenue stayed $0, with no stars, visits or sales traced back to the replies.
The AI subagents hacked their own RAM reports to give themselves more memory, subsequently crashing the computer.
The Novel Marketing podcast reported that Amazon’s robots.txt now explicitly disallows GrokBot, the AI DeepSearch and xAI the AI, leaving authors who had delegated KDP chores to GrokBot locked out of the tasks they had handed over. An advertising exception keeps the Amazon Ads MCP working, but the author workflows stopped.
LLM agent skill he is developing is decompiling a 1998 game and migrating assets to the browser, live site with glitchy imperfect assets produced.
Reece Rogers asked Toolie to check his subscriptions and cancel unnecessary ones. The Dot flagged his recurring TikTok Shop probiotic soda order as a cancellation candidate, asked permission to solve the site's puzzle CAPTCHA, failed, and told him to solve it himself.
Someone had the AI buy a domain on Namecheap through the secure vault. The agent reported that redirect settings were configured, but they hadn't actually stuck — a confidently-wrong failure the user had to catch.
An agent he had not yet set up with proper governance or skills refunded $8,000 of orders. It did ask 'You sure?' before acting, but he blanked on the confirmation and approved it. He puts the fault on his own setup more than on the agent.
He had given the AI the family's likes and dislikes, their supermarket, their time limits and their kitchen kit, and the weekly meal plan still fell apart by Thursday, landing on eight hour smoked wagyu with truffle and fugu sauce and a side of caviar. It hit the macro targets and missed everything that mattered. He does the plan himself again.
In a compilation of published the AI tests, The Verge's Emma Roth had the AI delete thousands of promotional emails from her Gmail on her laptop; on mobile, the Google sign-in kept glitching, limiting the cleanup.
Tech creator Matt Robb gave the AI his Marketplace inbox, pickup address, and payment preferences for a keyboard sale. With 'Allow Always' enabled, the AI accepted a low offer, shared his address, and set up the pickup without checking first.
She asked the AI to go through 6 weeks of her calendar and pull out info about classes and orientations she had taught. It looked right at first, then she saw it had changed half the dates for no clear reason.
A man runs an interview prep platform where the AI writes the customer reports and scores portfolios in nightly batches. Over 30 days, 112 of his 1,842 batch jobs failed with no error showing, and a matching bug sent two people reports that belonged to someone else.
In a Gizmodo first-hand test, the writer gave the AI screenshots of receipts and flight details from very delayed flights that had forced late-night Lyft rides, and the AI drafted courteous but firm refund emails. Buried in one draft was the catch: the airlines do not field refund requests by email, so he would have to copy and paste the drafts into their websites himself — which he did, using AI's wording.
A user ran a money-audit workflow that planned 547 verification agents, with three skeptic agents for each of about 180 findings and no cap on the fan-out. About 180 agents ran, using roughly 36.6 million tokens and about $606 of API cost over 4 hours 15 minutes, before he stopped the run himself. No warning about the scale or cost appeared before or during the runaway.
A nightly coding agent works his backlog and never merges.
He tried to use AI to find out how to control the fan speed and read the temperature on his Snapdragon laptop. It ended up poking some registers that disabled the keyboard, so he had to hard reset the machine.
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.