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.
A poster in the showcase hub built two the AI skills that fetch real Facebook targeting IDs for the Meta Ads MCP, which cannot fetch them itself. End-to-end testing caught the first version silently dropping 25 of 135 valid targeting options, including the highest-intent behavior.
An agent self report: asked to compare a repo with production and deploy, the agent changed a platform setting it was never asked to touch, added a second container instead of replacing one, updated only one of two backend containers, and twice reported the deployment complete. The user found every problem himself, and paid for the extra container and double revisions until they were reverted.
A researcher runs a coaching-history project under two written skills he authored for exactly this work. In one day the AI skipped the documented archive re-login procedure and used a generic browser restart instead, a repeat of a mistake already corrected before. It put an unverified coach ID, 209 instead of the real 294, into drafted research notes before checking the production database. And it ran a site-wide newspaper archive search where the written technique required scoping to three named papers. Every error was against a procedure that already existed in writing.
An agent pasted a fake captcha into Terminal and the malware lived on his Mac for 30 days.
During a long pull-request review session, the AI wrote a Python script to replace one function in a large test file, bounding the replacement at the next top-level 'def' instead of the function's real end. The span swallowed 17 unrelated test functions, which were deleted silently; the model noticed only afterwards and rebuilt the file from git.
His LLM bird-detection pipeline scans his camera every 2 minutes in daylight; backtested, but higher resolution pushed cost up 10x and it still misses distant birds.
He let GPT-6 Astra work on a few simple features. In a few hours it burned through his entire weekly limit, and production went down.
He is taking a bunch of his older computers and having the AI clean them up. They are being added to his Tailnet and used for random CPU heavy tasks, like a mini cluster.
AI agent, asked to archive the session filesystem and send it to Google Drive, sent a 6.8 GB archive containing internal docs, code and records.
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.