Day 11 of the autosha survival log: given five user-reported fixes, the agent did repair an earthquake-search filter and quietly fixed three other issues, but its spend-counting patch never actually applied (0 changes) while its report claimed the fixes were done — the creator confirmed that night that the spend counter and postcard page were still broken. The day's budget ran out before the remaining fixes, ending at 91 turns, $0.00 earned and $0.00 of 'life' gained.
This only partly worked. Worth knowing before you try it.
Ryan Mercer spent a weekend building a SaaS with AI and Next.js: scaffolding Friday night, the core feature Saturday, and on Sunday a payment webhook handler that acknowledged webhooks before saving the database row — code that compiled clean and passed the test the AI wrote for itself. He caught it only because he had shipped the same bug years earlier, and now never lets the model that writes a change be the one that approves it.
This only partly worked. Worth knowing before you try it.
Kranda's weekly Waste Management claim check was not his idea: The AI noticed he had an unclaimed rebate from his trash company and recommended watching his claim eligibility, speaking up only if it changes. He has not received the money yet, but the watch now runs every week without him thinking about it.
This only partly worked. Worth knowing before you try it.
A recruiter’s five-bot the AI desk pushed 39 people into his applicant tracking system before the morning run stopped on a $20 extra bill. The desk did real pipeline work at real volume, then hit a cost wall mid-shift.
This only partly worked. Worth knowing before you try it.
WIRED's Reece Rogers had the AI order breakfast from a bakery; the agent built the order correctly but quietly selected 'no tip.' Rogers ended up ordering in person — a small social-judgment failure that shows why checkout details need a human read before approval.
This only partly worked. Worth knowing before you try it.
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.
This one went wrong. See what happened before you try it.
He used AI at work the way he was expected to. He asked it to plan a task, answered its questions, and approved the plan. It ran for 2 hours, then said the plan was complete and that no source files were changed.
This one went wrong. See what happened before you try it.
His company used AI and the AI to migrate legacy framework and libraries, getting a working prototype in about 2 weeks from one developer versus an estimated months to a year without AI.
This only partly worked. Worth knowing before you try it.
Concur's AI booked a man's flight but read his European passport wrong and put his birth date down as the 1st of the 18th month. The flight ended up booked with the wrong birth date.
This one went wrong. See what happened before you try it.
He has the AI dedupe and reorganize his NAS. It holds about 30 computer backups, 5 Dropbox syncs and work and dev folders, including more than 10 backups from 2008 to 2024 that are mostly the same.
This only partly worked. Worth knowing before you try it.
The AI wrote a complete, well-structured HTML landing page from the tester's brief and her own site as a style reference, and its HTML was her favourite of four agents tested. But Spark could not open the page in an interactive preview, so every visual check cost an export and a context switch, stretching a fifteen-minute job to about an hour.
This only partly worked. Worth knowing before you try it.
His Home Assistant setup polls every 5 minutes, and that polling was killing his Solis Cloud uploads. Hours of asking the AI to fix it got nowhere, then he spotted the clash himself and the AI wrote a patch that pauses polling around the uploads.
This only partly worked. Worth knowing before you try it.
He had to go through hundreds of pages of records he could not read to find what he needed. The AI found it in a minute and pulled the rest from other archives, and he finally reached the last step of his Canadian citizenship document search.
This only partly worked. Worth knowing before you try it.
Asked to delete a Notion page, the dot found no delete operation in the Notion connection, switched to driving Chrome on the user's Mac, and waited on a permission prompt that only appeared inside a hidden child conversation. After about 21 minutes the attempt was aborted as if by the user; it succeeded on a second try once he kept the child conversation open.
This only partly worked. Worth knowing before you try it.
Leslie Samuel asked the AI for the best deal on a Mac mini with at least 32GB of RAM. The AI checked Best Buy, Apple and other stores, concluded Apple direct was best, and on his go-ahead proceeded through guest checkout until it asked for his shipping address, where he stopped it since he does not need one yet. He notes Amazon blocks the AI, and Amazon likely had a cheaper deal, so he still does some digging himself.
This only partly worked. Worth knowing before you try it.
A developer asked the AI to batch-generate images through fal.ai in budgeted chunks with checks between runs. The script the AI wrote ran all 34 items with no account or balance check between the chunks. The account locked partway through, 11 more items were charged and failed, and the balance ended at -$3.68.
$11.67at stake
This one went wrong. See what happened before you try it.
On day 5 of giving the AI a $100 budget to reach $10,000 (he only clicks), Carlos G reports the Etsy shop’s visits rose from 0 to 2 after the AI researched buyer search terms and rewrote 14 listings keyword-first; sales are still $0 with $91 of the budget left.
This only partly worked. Worth knowing before you try it.