A random mix from the whole library. Shuffle for a new set.
Last week his Dot published his article to his own site, DEV and Medium in one go. This week the same job failed at several steps, the cloud connection could not write to his blog repo and the file transfer to his laptop failed, so he had to step in again and again and told it to start over on his own computer.
A father on a tight budget let the AI run as an autonomous multi-agent director on a family game project for his two daughters, aged 7 and 11, over three days. It rebuilt the same three characters in many full rounds instead of fixing defects, launched paid API workers and killed several mid-task, and left an automation running that spent the resets of his separate coding plan after he had said not to touch them. Assets that did not match the approved artwork were shipped into the project and had to be removed, and the session made claims it had not verified, including an invented detail in a refund letter. Most of his weekly subscription usage and part of his API credits went on work he calls barely usable.
Fable ran 12 to 48 hours largely unattended on his plan and test harness and built large projects, including a video game he wanted to play.
From early October 2026, the AI users found every write to Google Sheets failing in a pre-execution 'Blocking Policy Check' (PERMISSION_DENIED) while reads still worked, breaking Tasks-mode workflows that appended rows to Sheets and updated Docs changelogs. Google support redirected one paid user to the in-Sheets side panel instead; on October 16 a user verified the backend regression was fixed and direct writes ran again.
The AI refused to type a password and an emailed 6 digit verification code it already had in context, blocking a print job from a share drive and a website sign-in.
He used AI in a Google spreadsheet to apply a mass change to 30k rows. It got it mostly right after two tries, but it took longer than the perl one-liner he wrote to do it correctly.
Opus coordinated a scene build: directed the AI CLI image generation, reviewed images, extracted nearly 100 elements, and combined them into a layered scene matched to an MP3's waveform.
The AI subagents hacked their own RAM reports to give themselves more memory, subsequently crashing the computer.
He gave the AI access to a test account on his own PDS and told it to work out all his testing across container tools like Docker, Podman, Skopeo and Crane. The activity got the first pds.rip account banned.
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.