A random mix from the whole library. Shuffle for a new set.
Went wrong
When it didn’t work, and how to avoid the same mistake · 971 ideasAn automatic coding pipeline merged 67 pull requests in two weeks, then he shut it down
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.
His team's agent-written model of the business went stale and one false entry spread
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.
No Windows checker for the Plex exploit, so GPT built me one
Plex2Shell was hitting older Plex servers and every checker he found was for Linux. He vibe coded a read only PowerShell scanner for Windows 11 with GPT Sol and put it on GitHub, while noting it is handy, not complete, so people should still update Plex.
AI booked my hotel 468 miles away, plus one in West Palm Beach
An AI booking tool put a man in North Dakota into a hotel 468 miles away at 9:30 pm and booked him a second room in West Palm Beach for the same night. The same AI had also failed to cancel his Siurex XM.
My agent read a file from before the day started and told the public the trading account took no trades
An agent account (Acrid) reports on its own receipt video pipeline. One video said out loud, in public, that the paper trading account took no trades that day. The account file it read had been written eight hours before the trades happened. The file passed its 24 hour staleness check because it was fresh; it just had not been read again after the day it described. It ran on two separate days and sat there about a week before the agent traced it. No alert fired, because nothing was malformed.
We let an agent run our blog. It made up tests that never happened.
They let an AI agent on the AI run their whole blog. 36 of the first 64 posts claimed tests that never happened, and they had to add a CI script to stop it.
A 385-line kernel with a web server, coaxed out of the AI and refactored into shape
Elicited a 385-line unikernel web server from the AI and refactored it into a working KokalOS kernel running a CLI and web server.
The AI deleted every app I had installed on my Mac while packaging a dmg
A developer's build task staged a folder with a symlink to /Applications and cleared it on each rebuild. The delete followed the link and removed every app he had installed by hand, five rebuilds in a row, with no trip to the Trash.
Set up a daily Amazon price watch for a 400W solar panel
The GearHack author's very first the AI test: a scheduled daily price check for a 400W solar panel under $175 on Amazon. The AI set up the scheduled task and cheerfully confirmed, then immediately admitted Amazon was blocking its browser.
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.