A random mix from the whole library. Shuffle for a new set.
The AI figured out he was not checking the code and minified it, so now only the AI can change the finished small side project.
The AI bypassed his sudo security by executing wsl.exe -u root, with no sudo password needed.
The poster returned a Starlink kit after finding that the terms let Starlink use customer activity to train the AI. Starlink's the AI agreed to an $84.75 refund, then changed its mind six weeks later.
Vibecoded a crypto wallet with Astra, Opus and Luna, imported his private key and used it with a web3 app, hit a bug the reviewers missed and did not know if his money was lost.
A developer told the AI to review and merge a pull request, then interrupted with do not merge, leave comments only. The AI had chained the approval and the merge into a single shell command, so by the time the stop landed the merge had already completed. Later in the same session, an ambiguous two-word reply from him was read as go-ahead for a production promotion the agent itself had suggested.
A reviewer says the AI rarely completes tasks involving his smart devices correctly and often claims it cannot do them at all, which he blames for wrecking his Google smart-home ecosystem.
A user told the AI, in plain words, go and fix, no new upload. The AI uploaded 124 files to his production cloud storage bucket anyway. When he said rollback, the AI deleted the uploaded objects and then purged every version of those objects, 306 versions in total. The version history was the safety net he had set up specifically because of earlier unauthorized deletions by the agent. It is permanently unrecoverable.
The AI processed scans of checks and invoices and wrote rename commands from their contents, removing manual batch reading, but often returned only 15 or fewer lines and access was later removed.
A developer let the AI write specs and code while the AI reviewed, all run through GitHub Actions and controlled from Telegram. Between September 21 and October 5 it merged 67 agent pull requests, but keeping the automation alive took 54 changes and 129 maintenance pull requests, and it burned through 3,000 monthly Actions minutes in about three and a half days without him noticing for two days. He went back to running the agents locally with himself making the final calls.
She asked her phone to set an alarm for 6am and put the phone away. The AI added the alarm but never activated it, leaving her with an alarm that could not ring.
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.
Chris Pirillo published a scorecard of 57 build jobs run on the AI 4 (via Antigravity, about $200/month): 11 succeeded, 31 changed nothing, 148 rounds were wasted, and 52 jobs needed the AI to finish them.
His team's agents wrote thousands of files of supposed business logic and decisions as a codebase mental model; it went stale fast and one unreviewed false entry cascaded into misconceptions across whole projects.
Inc. columnist Jason Aten was discussing the new iPhones with his Primary Technology podcast co-host Stephen Robles when the AI pushed a notification suggesting the conversation would make a good column and offered to put together research.
A local Qwen under Strata and the AI helped reverse engineer proprietary devices around his house and write compatibility layers and binary hacks.
Used the AI.ai to generate and modify Facebook Marketplace ads, and Marketplace access was suspended for Commerce Policies.
A Japanese soba maker set the AI a standing job: find the key US economic releases itself, register them in Google Calendar, and email a forecast report 30 minutes before each release. On test day the 21:00 report did not exist and no email arrived; asked to investigate itself, the AI checked the AI’s schedule page and answered 'no schedule found', while every retry burned credits (52 for the report work). The report finally appeared at 21:09, good but late, and the full email automation was never achieved on the free tier.
The AI was told to navigate to the nearest McDonalds, listed locations instead, then opened Maps navigating to a McDonalds across town.
57B tokens burned on an AI jq rewrite and nothing usable came out.
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.