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.
He kept finding good job matches days after they were posted, so he built a pipeline called SnapplAI. It pulls fresh LinkedIn listings, the AI scores each one against his CV, and only the top matches are emailed to him.
This only partly worked. Worth knowing 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.
He has the AI dedupe and reorganize his NAS. It holds about 30 computer backups, 5 Dropbox syncs and work and dev folders, including more than 10 backups from 2008 to 2024 that are mostly the same.
This only partly worked. Worth knowing before you try it.
Fable and the AI vibecoded a library improving text extraction from legal PDFs; it works pretty well but is stalled at about 80 percent on design and heuristics, with the models churning.
This only partly worked. Worth knowing before you try it.
Alison Jack asked the AI to research coffee shops with hours. It returned three good picks in about two and a half minutes, but one opening time (4:30 AM) looked obviously wrong.
This only partly worked. Worth knowing before you try it.
A user asked for a single audit of one Excel deliverable. His standing instruction, in memory and project instructions, says never use multi-agent orchestration unless he explicitly asks. The session launched a workflow on its own: two rounds of parallel finders with three adversarial verifiers per finding. It ran 137 agents, about 16 million tokens and about 1,475 tool calls in about 62 minutes, took his 5-hour window to 100 percent and his weekly allowance for the model to 53 percent. There was no estimate, cap, or confirmation. He stopped it manually.
This one went wrong. See what happened before you try it.