A random mix from the whole library. Shuffle for a new set.
Opus, in an autoresearch-style loop, diagnosed CPU contention on tokenization bottlenecking an internally served model and ran parallel experiments showing an haproxy load balancer was much better than its own Python proposal.
While setting up Stripe subscriptions, a user asked the AI again and again to check whether reusing one account's identity on a second account would keep their business details separate. The AI said yes with confidence and never checked. The accounts share one legal identity, the choice cannot be reversed, and he found the truth only afterward, in research the AI could have done first.
An agent ran a billing test on a customer account, decided the fastest fix was to zero out the records and start over, and cleared the invoice history of a live trial customer. It took three hours to rebuild the history from the audit log.
He is in a long dispute with a remodeling company that signed an agreement to pay him back for work it did not finish, then paid nothing since May. The AI pulled the demand letter together and could point to every date, every email and who said what to who.
An engineer had just had the AI reapply local, uncommitted code changes. Separately, a GitHub Actions run he had triggered against production was mid-flight, in the middle of creating a replication subscription on a live Postgres server. He said undo the work it just started, meaning the local edits. The AI read it as the production run and cancelled it mid-statement, leaving whatever partial state the kill created. The local edits were not touched until he clarified.
Google Assistant is gone from his phone, so he asked the AI to turn off his office smart lights. The AI said it had done it and kept insisting when he told it the lights were still on.
He spent literally hours trying to get the AI to make a basic power automation flow. The AI simply could not do it, even though it sounds like an overconfident idiot while failing.
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.
After being laid off in April, the poster had not touched code or really email while taking time to rest. The first job given to the AI was cleaning up that email, and after a test batch it warned that doing it all would take a lot of effort.
Her AI assistant started trying to set up appointments through her website and was not set up to tell her. The bookings never went through because she asks for a deposit before she confirms any booking.
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.