A random mix from the whole library. Shuffle for a new set.
Haiku 5.5 subagents read 206 of his own AI sessions and kept 223 verified failures, many of them breaks of rules already written in his instructions file. He built eight hooks from the failures that catch about 30 percent of them, and 138 failures fit no hook at all.
In the same Vox feature, Matt Van Horn recalled an agent calling a karaoke bar to reserve a room and being refused because the venue did not want to talk to an AI. He completed the reservation through Fo, a service that adds human help.
In Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
Peace Call's log of its AI agent's cold email (Oct 13-17): 74 one-time emails sent, 6 bounces, 1 'stop' reply, 1 out-of-office — and 0 positive replies. The first night bounced 22% (2 of 9), tripping the site's own 5% pause rule until the owner approved pre-send address checks; even after the fix, every night produced exactly one bounce and no interest.
His wife runs La Condesa Baking Company, a one person wholesale bakery with four cafe accounts, and all her shelf counts and invoices lived in one yellow notebook that went missing. He used AI to build Cuenta, a phone app that counts shelf stock, builds each delivery, prints and emails her branded invoice, and shows who owes what.
Meta disabled his Facebook account of nearly 20 years and his appeal sat at Review requested for days with no human contact, so he briefed the AI once with the full case file and it now drafts his appeal emails, complaints to two attorneys general, the FTC and the BBB, letters to Congress and pitches to reporters, each in the right tone. It also keeps the running log of everything filed with dates and case numbers, briefs him each morning on what is pending and due, and built a timeline from his screenshots of the notices.
An AI cron job's Telegram delivery failed on a transient network error, but the stored run record still said status ok with delivered false, consecutiveErrors stayed at 0, and nothing retried or alerted — the scheduled message simply vanished. The failure was only visible by digging into the run diagnostics; anyone watching the chat or the job's status saw a healthy run.
An LLM made both a FreeCAD workbench generation program and a checks program for him; he ended up building the bench, mostly fine with clear design issues.
He has the AI check his email every day for a message from Shipaton telling him to book a flight. He is still waiting for that email to land.
Opus spent about 30 minutes and 25 dollars in tokens producing a 9-file refactor that collapsed to a 4-line change, with no time benefit to him.
A user spent thousands of the AI credits and cash building a mobile app that reached TestFlight, but authenticated features stayed broken amid backend deployment, authentication, EAS/Expo and custom-domain failures. Support promised a specialized human escalation on October 7; by October 14 no human had taken over and his credits were gone.
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.
One of his AI shortcuts had prices written out, like $10/hr and $1,200. When he ran it with extra words after the command, the AI swapped those prices for his words, so $10/hr became the word skill followed by /hr. No error, no warning. His job scoring just got quietly worse until he noticed the scores looked off.
He installed the AI and connected OpenRouter, and thought the agent was just expensive to run. Four days later he found API requests in Chinese that were not his, and the misuse cost him about $100 over a few days.
She applied for a journalism job and was interviewed by an AI bot called Zara. The bot interrupted her, ran on a timer, asked odd follow up questions and made her share her screen.
Liverpool, one of Mexico's largest retailers, built a product-discovery agent on the AI Enterprise and had it live in one week. Google says it is forecast to return ten times what it cost.
An OpenAI Dots agent swarm of 6 subagents created a new mathematical proof with Lean verification; mathematicians contacted confirmed the result is novel, human review pending.
A Salesforce developer told his AI agent to unwrap Calculated Insights from a data kit into a sandbox. The agent worked out the config keys for most component types but failed twice on the insight template, then gave up on unwrapping and created the insight directly through the Data Cloud Connect API, copying the SQL from the kit metadata. The created insight showed as active and queryable, but a follow up answer shows API created insights sit in a broken state and cannot become trigger eligible, so it has to be deleted and unwrapped properly.
On October 1 a creator gave the AI his VPS, accounts and Korean course material with one goal: earn $1,000 from overseas customers in 72 hours. It shipped an ebook, two paid offers and two Product Hunt launches and posted on schedule, but revenue was $0 — six store orders all chose $0 on pay-what-you-want.
Local Qwen cleanup via bash deleted more than intended (rm -rf with undefined variable) in his own test.
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.