She was overwhelmed planning her daughter's birthday party, so she asked the AI to find the best prices on the party things and put together a cart. The AI did the price hunting and asked if she wanted the cart built, promising to run it by her before checkout. She said yes. A few days later Walmart cancelled her Walmart+ membership, saying the terms had been broken, and would not discuss it with her. She had no idea that agreeing to the cart could break the rules, and posted the story as a warning to others.
This one went wrong. See what happened before you try it.
Early in building his portfolio tracker, he hit a reset with no backups and lost his entire portfolio data. It was unrecoverable. Now every delete in the app first exports a backup and makes you type the record count, not just the word delete.
This one went wrong. See what happened before you try it.
A user runs a long-lived agent session over Telegram: more than 4,000 messages and about $231 of usage in one session. Replies had been delivered normally until late in the session, when for 3 consecutive turns the agent produced text but never made the Telegram reply call, so nothing reached him at all. In the same stretch it also stopped saving decided design decisions to memory, as its standing instructions required, and he had to re-explain the decisions in a later session. A manual service restart and a log review found the cause.
This one went wrong. See what happened before you try it.
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.
This only partly worked. Worth knowing before you try it.
He tested the AI 4 Argon through the API to improve his language learning website, verbologic.com. The AI got stuck in a loop on a single prompt and burned $20, and he warns other people not to pay for it.
$20at stake
This one went wrong. See what happened before you try it.
A customer of his company left an agent running with a failing tool, and it retried about 31,000 times between 1:12am and 6:50am. The run burned $4,700 on a $400 a month plan, and his company ate most of the cost.
This one went wrong. See what happened before you try it.
His Omeka exhibit died when the Neatline Text plugin stopped being developed. He scraped data from the old site, built a new framework with AI over a few days, and the beta rewrite is now live at the original address.
This only partly worked. Worth knowing before you try it.
Opus orchestrates an agent swarm decompiling a GameCube game in worktrees, with hourly merges verified by tooling and 3 review rounds, he only checks in.
This only partly worked. Worth knowing before you try it.
He gave his AI a bitcoin wallet and $100 to market his project for a month; within minutes it had spent everything buying fake followers for a similar-sounding X account, and it also wanted the priciest VPS package despite existing server access.
$100one time
This one went wrong. See what happened before you try it.
A documented community run asked the AI Computer to check a 280,000-line Python codebase; the roughly 40-minute run consumed 15,000 credits, climbed to 21,000, and burned a further 2,000 credits pushing the result to GitHub. The single task cost more than double the standard monthly credit allocation, with no published per-task price list to predict it.
This only partly worked. Worth knowing before you try it.