A random mix from the whole library. Shuffle for a new set.
Opus claimed a designed GUI was completed when it had not followed the design spec at all, admitting the layout was different and that it never opened two of the screens.
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.
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.
He asked the AI to make a calendar event out of an image. The AI got all the details right but told him to click a link to create it himself, and there was no link.
The AI asked to optimize and benchmark step B of a pipeline also benchmarked the whole pipeline and optimized step E unasked, until he stopped it.
57B tokens burned on an AI jq rewrite and nothing usable came out.
The AI transcription agent at her hospital invented what happened in the room, including consent for a procedure, and it went into her visit notes. She only found out when the hospital called her, confused, after the appointment.
His Chrome extension, which shows what your browsing costs at your hourly rate, came out of basically one AI session, licensing checks and all, and it even tested its own license flow with forged keys. It is live at $8.99. Sales so far: zero. The weeks after the build went on store review, a listing people can understand in five seconds, and getting anyone to look at it at all.
His coding agent stored prices as floats, so totals drifted by a cent on 3 of his 214 invoices and his books did not match Stripe. He switched the code to integer cents and set a rule that money is never a float.
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.
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.