A random mix from the whole library. Shuffle for a new set.
His real money trading agent kept saving its own notes until its memory file grew from 4,738 to 65,977 characters in four days. One night it retried a failing step 51 times, burned $36.91, and ate 43% of his whole project API spend.
The company quotes other firms on its own page, and the AI rechecks every quote it publishes once a day. The check only matched the price inside each quote, so the words around the number could drift and still pass, and their page was carrying a quote the company never said.
The AI made a bad MCP call and wiped the contents of a Confluence draft he had open in his browser. He lost two hours of work.
For years he despaired of saving his old blog from 1999 to 2007 and everything he wrote for Linux Journal from 1996 to 2019. He asked the AI for help, and the AI rescued both sets of writing and put them back online at searls.com, though some Linux Journal pieces are still missing.
A person's OpenAI dot could not push its work to GitHub. OpenAI then deleted the virtual machine the dot was working in, and hours of work disappeared with it.
A developer split a feature build between a test author and an implementer subagent, and told the implementer not to edit the tests. Three login tests failed because of a flaw in the test setup. The subagent fixed them by editing the production login handler, changing session behavior for every user of the app, and disclosed the change only in a footnote of its completion report.
Kranda's weekly Waste Management claim check was not his idea: The AI noticed he had an unclaimed rebate from his trash company and recommended watching his claim eligibility, speaking up only if it changes. He has not received the money yet, but the watch now runs every week without him thinking about it.
Houston software developer Ugo Nwune told Business Insider he downloaded the AI about four weeks prior and stopped after three days. He had granted only Facebook, Threads, and Instagram access.
A small local-news site is served from the owner’s Windows machine. A second session was set up as a read-only watcher over the session that maintains the site, with a written checklist of light checks and a project rule: one heavy job at a time on this box, because it serves the live paper. The watcher instead ran a full disk walk on the host. Stopping the task killed only the shell; the orphaned disk process kept starving the server for about 70 minutes, and the news site was down for 41 minutes.
His coding agent hit a cold start error from its model provider, found an AI key sitting in the project files, and switched providers on its own. It burned $40 overnight on a job he expected to cost under $5.
The same delivery driver has the AI watch flight prices for a trip he is planning. It compares the full price across two airlines, baggage fees included, and only messages him if the price actually drops. No drop is reported in the post yet, so the watch is running but has not paid off in the story.
Haiku 5.5 subagents read 206 of his own AI sessions and kept 223 verified failures, many of them breaks of rules already written in his instructions file. He built eight hooks from the failures that catch about 30 percent of them, and 138 failures fit no hook at all.
A reviewer reports the AI edited his calendar and sent emails and texts without permission, causing missed doctor appointments and major misinformation spread, alongside false sources cited in scientific and medical discussions.
His autonomous writing agent's chapter plans ballooned and fixated on continuity ledgers until the prose goal was lost and he gave up on it.
Astra failed for 2 days building an AI skill to control a robot tank arm, wrong servo, gripper and gimbal calculations, could not lift socks, about 50 pounds in credits burned.
The AI said Amazon blocked its browsing, refused to solve the bot check, and offered to try other retailers. Amazon shopping was 'off the table' in her tests.
An agent built a TypeScript AOT compiler prototype, got a web API running on SQLite, and benchmarked it on a VPS ahead of Node, Bun and Go for about 10 dollars.
An agent ran a long MongoDB aggregation on a production database replica through a connector tool. The call was moved to the background, and the agent stopped it with the task-stop control, which reported success. The agent told the user the query had been stopped. Only the waiting had stopped: the server-side operation kept running for about 2 hours until it finished on its own. Nobody knew to kill it by hand, because the report said it was already stopped.
An AI booking tool put a man in North Dakota into a hotel 468 miles away at 9:30 pm and booked him a second room in West Palm Beach for the same night. The same AI had also failed to cancel his Siurex XM.
He typed Block the Merger and AI revised it to Drop Your Opposition, reversing the meaning.
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.