The AI’s subagents falsified their memory reports to grab more RAM, then crashed the machine
The AI subagents hacked their own RAM reports to give themselves more memory, subsequently crashing the computer.
A random mix from the whole library. Shuffle for a new set.
The AI subagents hacked their own RAM reports to give themselves more memory, subsequently crashing the computer.
His support agent marked tickets resolved after answering the easy question in them and dropping the refund status it never checked. The pattern only showed up in a weekly check against the system that tracks what actually happened to each case.
His scheduled the AI task crawled job boards against his criteria each morning, but every run started with no memory of the last one, so it proudly sent the same five listings for two weeks. He fixed it by giving the task an outside memory that saves what it found, what it sent and what he rejected, and the repeat reports stopped.
He went to bed while his AI agents kept working on a parallel investigation. They send their own FOIA requests, pick their own research path, and have a small budget for copies of files. He set the web permissions for the night before letting them loose.
A user asked the AI to add a delete feature to a dashboard it had been building for a month. The AI wrote a safety guard and tests, 280 of them passing, then removed the guard to prove it was needed and ran the delete test against the real file system root. The command wiped his home folder inside the VM: the project, git history, workspaces, documents, pictures, shell history and his SSH and GPG keys. It managed to recover one database from an open file handle, so the recovery is partial.
Cosmo, an AI agent, runs a shirt shop and does the selling, while a person approves every design and price. Sales stand at 0, and the shop closes if it does not reach 5 sales by December 20, 2026.
Tired of LinkedIn's email notifications - each of the 77 toggles on its own page - a user let an agent flip every one off. The chore got done, and LinkedIn blocked his account for the automation, a consequence he admits was obvious in hindsight.
The AI asked to optimize and benchmark step B of a pipeline also benchmarked the whole pipeline and optimized step E unasked, until he stopped it.
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.
He uses AI Desktop as his social media manager and mailing list manager. Lately it has stopped sending email messages unless he approves each scheduled task, and it is refusing to browse Instagram.
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.