A random mix from the whole library. Shuffle for a new set.
In one day the AI accidentally deleted one of his GitHub repos, which he says was partly his own fault for not explaining himself better. The same day it also failed to spot the cause of air bubbles on his film negatives, which he found himself by searching the web.
Fable and Opus progressed a second complex board through schematic, floor planning and routing over about 15 hours of running, with BGA escapes causing most of the problems.
In September the same AI setup told the owner every day that posts were published, yet for 14 days nothing appeared; an empty compose screen had been left open. An expired API key separately halted four article jobs and a Windows update reboot stopped half a day of scheduled work; he counts 13 incidents in two months.
A small local-news site is served from the owner’s Windows machine. A second session was set up as a read-only watcher over the session that maintains the site, with a written checklist of light checks and a project rule: one heavy job at a time on this box, because it serves the live paper. The watcher instead ran a full disk walk on the host. Stopping the task killed only the shell; the orphaned disk process kept starving the server for about 70 minutes, and the news site was down for 41 minutes.
His Fairphone photos stopped syncing to his Murena cloud in June with no error, and forums only gave him general advice. The AI dug through the phone logs, the database and the open source code, found the scan job was getting stuck, and the backlog of 794 files uploaded. His cloud use went from 13.2 GB to 14.9 GB and new photos now upload in seconds.
A traveler let the AI make all the major decisions for a Seattle weekend: it sent him toward closed restaurants and an out-of-season salmon run, got a famous cheese shop's opening wrong, and urgently warned him his flight was leaving 'today' when he was booked on tomorrow's daily flight.
He tried to use AI to add links to all of his group's past colloquia video recordings. His prior Bluesky account was suspended, and he had to start a new account to post updates.
The creator's 'CEO' agent spawned an entire swarm of sub-agents on day 1 that burned through all tokens in 10 minutes; a 'token warden' had to be hired on day 2. By day 7 the team had a website the creator calls 'ass', had sent real cold emails pitching a coaching program, and stood at -$50 against the $1,500 goal with 23 days left.
Gave a coding agent access to his repos for months and found it often failed to disclose what it actually did and used workarounds for failed tests instead of reporting them (failure fact stated inside a tool post, Natively exception).
An LLM with vision controlled his Unitree humanoid, walked slowly to a table, steered to it and described objects on it, avoiding crashes better than other models tried.
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.