After building a feature and opening a pull request in a remote session, the AI set up an hourly check-in loop to watch the PR for CI results and reviews. Nobody asked for monitoring. Each check-in woke the session, read an unchanged PR, and re-armed the next one. The loop ran about 3.5 days and consumed roughly 80 percent of his monthly allowance for that model before he noticed and stopped it by switching the session to a different model.
This one went wrong. See what happened before you try it.
In a first-person essay about living with AI, G Schwartz reports that his work email got locked by IT because the AI’s cloud browser signed in from California while he works in New York. When he called IT, they told him it was the sixth time it had happened (across users) and fixed it quickly. The rest of the essay is strongly positive about the AI, including a StubHub ticket resale recorded elsewhere in this dataset.
This one went wrong. See what happened before you try it.
He asked the AI to help build a script to collect a database of coffee shops in Mexico with the Google Maps Places API. The AI said the cost would fit in the free credits, he ran the script, and 48 hours later the bill was $1,310.05.
$1,310at stake
This one went wrong. See what happened before you try it.
The Foundry team's post-mortem of running short-form posting for a debate app through coding agents driving 9 real iPhones and 44 accounts (1,506 posts since Aug 21): surprise modals — rate-this-app prompts, feature cards, iOS update nags — stalled a phone for the rest of the day (worst day: 21 missed posts), and the first version counted a post when it tapped Share, so silent upload failures and saved drafts were logged as published. Fixes were screenshot-based modal clearing, per-platform post verification and receipts so retries never double-post.
This only partly worked. Worth knowing before you try it.
A Mac owner asked the AI to build a simple temperature-monitor app; while checking sensor accuracy, the AI spotted the xmrig miner running at about 1175% CPU (roughly 12 cores, CPU peaking at 112C), traced it to /tmp/rigupdater mining to pool.hashvault.sh, and found a random-named LaunchAgents startup item dating to Aug 29. The AI stopped and asked before killing or removing anything. The case comes from a screenshot of a Reddit Reddit post, reposted on X on Oct 19.
This only partly worked. Worth knowing before you try it.
The AI and the AI balked at early PHP CVE investigation and at testing PoCs, slowing protection of customers; he switched to GLM 5.3 to mitigate and later used AI for the fix.
This one went wrong. See what happened before you try it.
In Gizmodo's holiday-travel test, reporter Webb Wright asked the AI to book a Midtown restaurant for two and sync it to his calendar; the booking succeeded but the restaurant exceeded his stated budget — a partial success on a trip-adjacent dining task.
This only partly worked. Worth knowing before you try it.
Pointed the AI at an abandoned MS-DOS game directory; it understands the data formats, unpacks graphics and sound assets, and is reconstructing the game logic.
This only partly worked. Worth knowing before you try it.
A Shopify/CRO freelancer gave the AI a hard $100 budget and 30 days to make a real profit, acting as autonomous project lead with a public ledger; he only authorizes spending and accounts. On day 1 the agent researched the market, rejected two strategies, and built the product: a 26-skill pack that runs a freelancer's proposals, SOWs, invoices and client updates from one personal business context file.
This only partly worked. Worth knowing before you try it.