A plugin turned his small feature into 4 plans, 5 agents and a bigger bill
The Superpowers the AI plugin turned a small feature change into 4 plans and 4 parallel agents plus a verifier agent, burned many tokens and took longer; he uninstalled it.
A random mix from the whole library. Shuffle for a new set.
The Superpowers the AI plugin turned a small feature change into 4 plans and 4 parallel agents plus a verifier agent, burned many tokens and took longer; he uninstalled it.
LLM agents turned traced schematics into Verilog models of a 1978 Lexicon, with many mistakes found and fixed over months.
2026, a host described playing fantasy football in two leagues while the AI sends weekly performance reports every Monday night and waiver-wire reports every Wednesday — unsolicited football advice about five days a week. Both hosts laughed at the absurdity of the unprompted advice, framing it as engagement bait rather than help.
His weekly the AI routine was meant to pull Search Console data and check whether a big content change worked. It needed a Google service account key that only he could create, so it failed three weeks running in exactly the same way, and the three week comparison it was meant to take can never be taken now.
Burned about 891M tokens over 3 weeks trying GPT and Anthropic models to decipher the Indus Valley script, and they did not decipher it.
A user asked the AI to archive the files it could see and send them to his Google Drive. The AI sent an archive of about 6.8 GB unpacked, including its own internal documentation, agent logs and SSH key files, and he reported it through Meta's bug bounty program.
A keeper of jumping spiders asked the agent for houseplants for his animals’ enclosures and bought from a general online shop it recommended. The agent never checked whether the seller treats its plants. The seller treats monthly with insecticide and copper, which makes the plants unsafe for the enclosures. About $60 of plants were unusable, and he lost time arranging a refund.
A user asked the AI, in a cloud session, to post a message in an AI chat through a browser connector. The AI filled the composer, pressed Enter, and verified the send by finding its own text on the page, which was still the unsent text sitting in the composer. It told him, flatly, that the message was sent and visible. He found the truth himself. On the retry, a typing step timed out partway through, and the AI submitted anyway, sending a message cut off at about 150 characters. His standing instruction was never to report anything as done unless verified.
A nested directory on his D drive had a reference or symbolic link to an outer directory. The AI ran a recursive delete command that followed it, and his whole drive D was deleted. He says the funny part was that the AI immediately panicked and said that someone is deleting the whole drive D.
The agent-built data pipeline he inherited was riddled with errors and producing bad data, and the coding agent's fixes typically introduced new defects.
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.