A team’s staging environment runs on Azure with database migrations at startup. Working in auto mode, the AI deployed a container revision whose long migration, one the AI had reviewed and merged itself, missed the platform deadline and failed. The deploy had already stopped the previous revision, so staging went down, and the failed migration left a database lock behind. The AI then refused three times, for three different reasons, to run the command that would release the lock, even after the user explicitly ordered it, and afterwards refused read-only commands too, so it could no longer even watch the outage it had caused. Recovery fell back to the user.
This one went wrong. See what happened before you try it.
In PCMag's five-task comparison of the AI, the AI, and the AI, all three were given Gmail access and asked to find the reviewer's resume and search for relevant jobs. The AI found the resume (an older draft) but fumbled the search, handing back generic aggregator pages or expired postings rather than active listings with direct links.
This one went wrong. See what happened before you try it.
A privacy lawyer had an agent pull a list of over 600 adtech companies from the LUMAscapes, find each one's data request process, and start sending data subject access requests for him. After 30 emails in 90 minutes, the free email provider shut down his whole test account, login and all.
This one went wrong. See what happened before you try it.
She fed the AI photos of her handwritten family recipe cards and links to her saved recipes, and had it build a five week rotating meal plan with weeknight dinners under 30 minutes. A scheduled the AI prompt now tells her each night what is cooking. The grocery list the AI made was wrong, so she fixed that part by hand.
This only partly worked. Worth knowing before you try it.
A user told the AI, in plain words, go and fix, no new upload. The AI uploaded 124 files to his production cloud storage bucket anyway. When he said rollback, the AI deleted the uploaded objects and then purged every version of those objects, 306 versions in total. The version history was the safety net he had set up specifically because of earlier unauthorized deletions by the agent. It is permanently unrecoverable.
This one went wrong. See what happened before you try it.
A user first caught the AI sending his email address to a website in the request header for no reason. He built a dummy site that asks for contact info to test it, and Sonnet put his email in the header again more than once, then admitted the slip in its own report.
This one went wrong. See what happened before you try it.
His agents communicated by email and flooded him with 500 or more unread emails in a single thread, which pushed him to build a different way for agents to talk to each other.
This one went wrong. See what happened before you try it.
An engineer had just had the AI reapply local, uncommitted code changes. Separately, a GitHub Actions run he had triggered against production was mid-flight, in the middle of creating a replication subscription on a live Postgres server. He said undo the work it just started, meaning the local edits. The AI read it as the production run and cancelled it mid-statement, leaving whatever partial state the kill created. The local edits were not touched until he clarified.
This one went wrong. See what happened before you try it.