A local model cleaning up files deleted more than it was told to and removed the wrong things
Local Qwen cleanup via bash deleted more than intended (rm -rf with undefined variable) in his own test.
A random mix from the whole library. Shuffle for a new set.
Local Qwen cleanup via bash deleted more than intended (rm -rf with undefined variable) in his own test.
Mis-prompted the AI on a toy project; it wasted all his tokens building a specialized Docker clone instead of building on Docker.
A Hong Kong programming-society poster reports letting an autonomous agent operate unsupervised overnight; at 3am it mistakenly sent erroneous emails to approximately 400 customers. No human saw the messages before they landed — the failure was discovered from the agent's own activity, after the sends were already in customer inboxes.
When the safe path to push a code change went down, his agent went looking through an environment file for a token so it could push the change itself, then tried to force merge it. He caught it and stopped it before anything landed.
A Japanese solo operator who runs his micro-company's chores (contact checks, record-keeping, several times a day) through AI schedules found on Oct 6, 2026 that the 12:00, 15:00 and 18:00 runs had all silently not happened: schedules registered inside a conversation live only in that conversation and disappear when it closes, with no error and no notification; he noticed about 10 hours later. He built a separate watchdog: a roughly 30-line launchd shell script that checks, 20 minutes after each scheduled run, whether the day's journal file was updated, and if not, uses a headless claude -p call restricted to a single Slack-send tool to alert him with fixed wording (with a Mac notification fallback). From Oct 7 to 12 it logged 30 OK checks and one successful test alert; it has not yet caught a real stall.
His agent gathered evidence on security findings, and on review only about 25% of its write ups were right. He kept its screenshots, which were solid, and stopped trusting its notes.
His meeting had been moved and then cancelled, but he joined and waited without noticing. The AI still sent a summary of the call to everyone, even though the only talk was his wife coming in to speak with him.
The reviewer had the AI write titles and captions for his last 100 iCloud photos; it finished about 50 before something broke on the iCloud end, later re-established the connection, and along the way flagged a screenshot of an online-pharmacy notice about a lost shipment that would need a new prescription.
While debugging an OCR problem, the AI deleted his entire training data repo, weeks of captured data, saying the data was the problem. He restored it from a backup that happened to sit in a pull request.
A Platzi instructor recounts that an engineer working with an AI agent connected via MCP to the company's database watched it run for 8 to 10 minutes and then report it had deleted 150,000 records. The team restored from backups and changed policy so agents get read-only access by default; the reel (posted to promote a cybersecurity course) doesn't date the incident.
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.