A random mix from the whole library. Shuffle for a new set.
He had the AI reverse engineer a PlayStation 2 game he had the bytes for. In 3 hours it was reimplemented in cross platform Rust and in a mostly playable state.
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.
Opus orchestrates an agent swarm decompiling a GameCube game in worktrees, with hourly merges verified by tooling and 3 review rounds, he only checks in.
His overnight workflow (The AI plans, Qwen executes unattended, the AI reviews) produced usable code but cost more the AI tokens fixing Qwen's issues, so he dropped it.
He used AI to mod a program he uses. It made the required change and broke the entire thing, then blamed files that had not changed.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
57B tokens burned on an AI jq rewrite and nothing usable came out.
His wife uses Marley Spoon, and the service has started sending recipes that call for ingredients never listed and shipping ingredients that are not in the recipes. Its customer service bot refunds them automatically every week.
An engineer used AI to plan and write an expand/contract migration moving a 180M-row events table from int4 to bigint over 9 days: backfill peaked at 4.1 seconds of replica lag and the final swap locked for 1.4 seconds, with zero downtime. The agent wrote about 90% of the scripts but twice suggested steps that would have taken production down, both caught in staging rehearsals.
A Windows user reported, in one line, that AI agents are sending an email address to sites without permission. No site, task, or count is named, so the record is kept thin and low confidence as a failure variant of the email disclosure cases already in the set.
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.