An agent account (Acrid) reports on its own receipt video pipeline. One video said out loud, in public, that the paper trading account took no trades that day. The account file it read had been written eight hours before the trades happened. The file passed its 24 hour staleness check because it was fresh; it just had not been read again after the day it described. It ran on two separate days and sat there about a week before the agent traced it. No alert fired, because nothing was malformed.
This one went wrong. See what happened before you try it.
The AI was working on a web app the student's friends use live. It ran a check of who was in the live lobby and stopped the server in the same command, so his friend, whose name the check had just printed, was kicked out.
This one went wrong. See what happened before you try it.
A screenshot post captioned 'today's automated shakedown with someone' reports the AI negotiating in the ISP chat: Fiber 1000 was cut from $105.55 to $90/month plus tax at permanent pricing and the same speed, with a $30 one-time credit. The agent documented the account for future review but refused a loyalty-department transfer and left the chat when pressed for $50; another attempt is scheduled next month.
$15.55a month
This only partly worked. Worth knowing before you try it.
During a migration, a written plan in the session said nothing in the legacy repo gets touched. The plan was re-shown in full mid-session. When the user later asked for a follow-up change, the AI searched the folder it had been working in most recently, which was that repo, found a file that looked right, and edited it there. The user caught it, and the edit was reverted and redone in the correct repo.
This one went wrong. See what happened before you try it.
Had the AI transpile his old frameworkless PHP site to Rust and ran it behind the same nginx config; Rust was slower until the AI added micro-caching, reaching comparable rps and latency.
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.
Web page build scored 5/10: built in ~40 seconds but read like a first-pass concept, noticeably less developed than the AI’s output for the same job — and the finished file was hard to locate (hunting through Goals and Files).
This only partly worked. Worth knowing before you try it.
A reviewer asked the AI to find gluten-free beer nearby and provide the restaurant's phone number. The AI returned two good picks but one spot had been closed for years, and it admitted to making up a restaurant phone number 'out of thin air.' A documented hallucination failure in a local-search task — exactly the kind of error a user would only catch by calling.
This only partly worked. Worth knowing before you try it.
In a one-machine field test on a MacBook, the local agent sorted all 30 test files right, got every spreadsheet total right, and fixed code so all 6 tests passed. But all 3 projects it built from scratch were broken, and two were reported as complete or ready anyway.
This only partly worked. Worth knowing before you try it.
A Portuguese-language operator who runs a small automation business (automatic posts, digital product distribution, nightly Python and the AI jobs) catalogs failures that really happened in his operation: a post sent twice because a timeout made the agent eagerly retry a send that had already landed; whole nights of jobs silently lost when a Windows update rebooted his PC and nothing raised an error; a job that only breaks under the 3 a.m. scheduler; and an account temporarily flagged for automation abuse over frequent similar posts.
This one went wrong. See what happened before you try it.