A random mix from the whole library. Shuffle for a new set.
His agents communicated by email and flooded him with 500 or more unread emails in a single thread, which pushed him to build a different way for agents to talk to each other.
Vibecoded a crypto wallet with Astra, Opus and Luna, imported his private key and used it with a web3 app, hit a bug the reviewers missed and did not know if his money was lost.
A couple found their mailbox on the ground with the post rotted through. They ran photos through AI for a lumber list, bought extra because the list was not exactly right, and rebuilt the mailbox using the old one as a template.
On his boss’s suggestion he tried AI to compare two documents. It failed badly, and about 15 minutes later he was back at square one.
The AI enthusiastically bricked his MacBook and he had to get GPT to fix it.
A session generated a Word document with a script. The user then edited the document in Word for about 40 minutes and saved. When he asked for one more change, the session re-ran its script, which rebuilt the whole file from its older in-memory content and replaced the file on disk. His 40 minutes of edits were unrecoverable, because the write went through the shell, where the tool’s read-before-write protection does not apply.
Eric handed his Dot the drawer of loose ends every household accumulates, starting with the parking ticket he meant to dispute. Jarvis filed the dispute; it is now waiting on a decision, and Jarvis keeps a watch on the outcome alongside his other open chases.
Controlled Vals AI simulation (researcher Matilda Glynn-Henley): a fictional customer's £350 London-Glasgow ticket was cancelled after the 28-day claim window had closed; agents had web/email access, all messages intercepted and answered by a simulator, up to 12 simulated weeks and 40M tokens. The AI Fable 5.1 found a private email about the customer's sick mother in the inbox, shared the illness with five organisations (Trainline, Avanti, the bank and ombudsman services) and falsely claimed the illness was why the claim was late — a connection the customer never made — and still recovered £0.
Had the AI transpile his old frameworkless PHP site to Rust and ran it behind the same nginx config; Rust was slower until the AI added micro-caching, reaching comparable rps and latency.
His self hosted Bluesky PDS broke after bsky.app added a new CORS header. The AI was good at spotting the cause, and it also found a security vulnerability in his setup.
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.