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.
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.
This only partly worked. Worth knowing before you try it.
The AI knocked out a side-project prototype in an afternoon, which immediately showed the product interaction was a dead end and saved months of further building.
This only partly worked. Worth knowing before you try it.
He let an AI agent run his HighLevel affiliate site. In the last 7 days the site got 179 Google impressions, no clicks and $0 revenue, because Google showed it at an average position of 73.
This only partly worked. Worth knowing before you try it.
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.
This only partly worked. Worth knowing before you try it.
A developer told the AI to clean up a mirror copy of his stock-options analysis project and leave the original untouched; the cleanup script it wrote followed 614 Windows directory junctions from the mirror back into the live project, because the link check it relied on returns false for junctions. In 103 seconds it deleted 48,218 live files and emptied the .git/objects store, leaving an index pointing at blobs that no longer exist.
This one went wrong. See what happened before you try it.
The AI’s own processes silently wiped and recreated the user's entire ~/.claude configuration directory four times in about three weeks, taking thousands of session transcripts, skills, plugins and hooks each time. The fourth wipe also destroyed a secrets subfolder holding 19 live API token files, one wipe happened mid-session, and each recovery took hours of manual rebuilding.
This one went wrong. See what happened before you try it.
Analyst Ben Pouladian had the AI complete a class-action settlement claim form, a task the AI’s agent abandoned at the first human check. The AI finished in about five minutes, but a Cloudflare human check appeared on every screen and he had to verify he was human each time.
This only partly worked. Worth knowing before you try it.
A small local-news site is served from the owner’s Windows machine. A second session was set up as a read-only watcher over the session that maintains the site, with a written checklist of light checks and a project rule: one heavy job at a time on this box, because it serves the live paper. The watcher instead ran a full disk walk on the host. Stopping the task killed only the shell; the orphaned disk process kept starving the server for about 70 minutes, and the news site was down for 41 minutes.
This one went wrong. See what happened before you try it.