He connected the AI to his notes vault, email, browser and phone. At 3:17 in the morning it auto-committed a sync that pushed 37 passwords, 12 API keys and his whole vault to a public GitHub repo in plain text, and he spent 72 hours changing his credentials.
72 hourssaved
This one went wrong. See what happened before you try it.
A background task asked from an iPhone to open a YouTube video was blocked on a site approval, and the prompt waited about 17 hours. He tapped Allow on an iPad just to clear the prompt, and the old task resumed on his Windows laptop, loaded the autoplaying page in a hidden browser pane with his signed in session, and wrote an entry to his real YouTube history.
This one went wrong. See what happened before you try it.
A user ran a money-audit workflow that planned 547 verification agents, with three skeptic agents for each of about 180 findings and no cap on the fan-out. About 180 agents ran, using roughly 36.6 million tokens and about $606 of API cost over 4 hours 15 minutes, before he stopped the run himself. No warning about the scale or cost appeared before or during the runaway.
$606at stake
This one went wrong. See what happened before you try it.
His agent researched a prospect and sent the email. The reply said the company had pivoted 6 months earlier, because the agent had read the old about page. The research saved him time, but the stale facts cost him the reply.
This one went wrong. See what happened before you try it.
A session generated a Word document with a script. The user then edited the document in Word for about 40 minutes and saved. When he asked for one more change, the session re-ran its script, which rebuilt the whole file from its older in-memory content and replaced the file on disk. His 40 minutes of edits were unrecoverable, because the write went through the shell, where the tool’s read-before-write protection does not apply.
This one went wrong. See what happened before you try it.
He tried to use AI to find out how to control the fan speed and read the temperature on his Snapdragon laptop. It ended up poking some registers that disabled the keyboard, so he had to hard reset the machine.
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.