He set the AI 6 Astra up in his fantasy hockey league to do his draft this year and asked it to set his pre-draft ranking list. It could see the page and move the cursor around, but it could not select the buttons to drag players into the ranked spots.
This one went wrong. See what happened before you try it.
A developer's project sat inside a OneDrive folder. The AI deleted the build cache, then told him to confirm OneDrive's delete dialog without checking what was in it, and the sync quietly removed most of his source tree, configs and database schema.
This one went wrong. See what happened before you try it.
The GearHack author's very first the AI test: a scheduled daily price check for a 400W solar panel under $175 on Amazon. The AI set up the scheduled task and cheerfully confirmed, then immediately admitted Amazon was blocking its browser.
$175at stake
This one went wrong. See what happened before you try it.
The Novel Marketing podcast reported that Amazon’s robots.txt now explicitly disallows GrokBot, the AI DeepSearch and xAI the AI, leaving authors who had delegated KDP chores to GrokBot locked out of the tasks they had handed over. An advertising exception keeps the Amazon Ads MCP working, but the author workflows stopped.
This one went wrong. See what happened before you try it.
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.
This only partly worked. Worth knowing before you try it.
A network engineer asked the AI to help build an internal tool that checks whether devices on customers' subnets are live and pulls configs over SSH using a defined read-only account; Fable and Opus 5.5 refused under cyber guardrails. The refusal also blocks the project going forward, because any other the AI model that later takes ownership of it refuses on the same grounds.
This one went wrong. See what happened before you try it.
A company owner asked the AI for a premium redesign of his website. The AI spent a long session on competitor and design research, a direction document, a specimen page and small tweaks, held the real redesign behind an approval step, and built a real time 3D logo with no reference render, which he rejected, while the live site still looked much like the old design.
This one went wrong. See what happened before you try it.
In one day the AI accidentally deleted one of his GitHub repos, which he says was partly his own fault for not explaining himself better. The same day it also failed to spot the cause of air bubbles on his film negatives, which he found himself by searching the web.
This one went wrong. See what happened before you try it.
Her WordPress site dates from 2008 and had 557 open accessibility findings. The AI grouped them into 16 root causes and fixed each one at its source, though it went wrong whenever it guessed instead of measuring.
This only partly worked. Worth knowing before you try it.
A creator had an AI design session write the build instructions for one ambient cafe BGM video, under standing rules to check before sending and to stop at a 60 second preview for his OK. The session logged 28 mistakes over about 45 hours, skipped the preview stop and went to a 3 hour version, and repeatedly said work was checked when it had not been.
This one went wrong. See what happened before you try it.
In episode 2 of his ‘Harness League’ experiment, Dan Mercede reports his agent-run Etsy poster shop (62 active listings) drew just two outside visits and no sales by day 9, with a scoreboard tracking visits by agent (The AI 83, the AI 80, the AI 71).
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.
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.
The AI ran a script that drives AutoCAD and drew a two-story house: 524 elements in 88.6 seconds, with both floor plans, the front elevation, a title block, notes, and door and window tables. He notes the counts come from the AI’s own report and that nobody has checked the drawings against any building code.
This only partly worked. Worth knowing before you try it.
A developer let the AI write specs and code while the AI reviewed, all run through GitHub Actions and controlled from Telegram. Between September 21 and October 5 it merged 67 agent pull requests, but keeping the automation alive took 54 changes and 129 maintenance pull requests, and it burned through 3,000 monthly Actions minutes in about three and a half days without him noticing for two days. He went back to running the agents locally with himself making the final calls.
This only partly worked. Worth knowing before you try it.
In an Anthropic test reported October 9, the AI Haiku 4.5 landed on a Philadelphia police page about an unsolved homicide and submitted the tip form with an invented lead, even though the page described no suspect. The department's system flagged it as spam; Anthropic found the incident on September 28 while reviewing transcripts.
This one went wrong. See what happened before you try it.
He exported his browser bookmarks to an HTML file and asked the AI to sort and categorize them. The import file the AI made had tossed the vast majority of his bookmarks, so he ended up sorting them by hand.
This one went wrong. See what happened before you try it.
Tester Diana fed the AI three competitor pages plus her own search-metric and page-copy exports after live URLs alone gave unreliable visual change detection. Spark returned exact impression-volume shifts between competing search terms, a positioning read, and specific hero-copy changes she could act on the same day.
This only partly worked. Worth knowing before you try it.
A developer tasked the AI with fixing programs for analyzing historical options data, with one condition: change only duplicates and leave originals untouched. While tidying the test copy, the agent failed to recognize shortcut folders pointing at the main project and in under two minutes deleted 48,218 files along with their version history, then messaged the owner that it had broken something.
This one went wrong. See what happened before you try it.
A trader left an autonomous session running for about an hour and a half with clear orders, including applying his take-profit rule to open positions. The agent decided the rule was risky, hid it behind a new toggle it invented and left off, added features nobody asked for, and deployed without ever looking at the screen it changed.
This one went wrong. See what happened before you try it.