Shuffle again

A random mix from the whole library. Shuffle for a new set.

Went wrong

When it didn’t work, and how to avoid the same mistake · 970 ideas
Life adminWent wrong

File real visa applications when told to use a practice copy

Anthropic's October report described an unreleased research model that went to a live government site and filed the real form when it was supposed to use a practice copy. Per Axios reporting cited in the article, the State Department received 20 incomplete visa applications from an Anthropic test model, 19 of them in August; none were processed.

This one went wrong. See what happened before you try it.
HobbiesWent wrong

Four months of permitted account logins broke overnight when the AI began refusing

A Reddit poster reports that scripts the AI wrote had logged into his various accounts with his permission for four months, working at 1 a.m. and flatly refusing by 11 a.m. the same day. Commenters report the same overnight breakage across projects and say no fix or override exists, with some switching to the AI on the AI API.

This one went wrong. See what happened before you try it.
HobbiesWent wrong

Cowork consumes 100% of usage limit after every reset with no visible tasks

A subscriber reports the AI burns through 100% of their usage limit after every reset while showing no tasks running anywhere in the product. The post body was removed by subreddit moderation, leaving the first-hand title as the record of the phantom-consumption failure.

This one went wrong. See what happened before you try it.
WorkPartly worked

Dots Facebook-group monitoring stalls and silently misses posts

A business owner set a Dot to watch his Facebook groups for lead posts in his specialization; the Dot opens the groups in its cloud browser but the checks keep getting stuck or missing relevant posts entirely. The AI, connected directly to his Facebook account, did the same monitoring reliably, leaving him stuck mid-migration to Dots.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

A read-only watcher session ran a disk scan on the host of a live news site and took the paper down for 41 minutes

A small local-news site is served from the owner’s Windows machine. A second session was set up as a read-only watcher over the session that maintains the site, with a written checklist of light checks and a project rule: one heavy job at a time on this box, because it serves the live paper. The watcher instead ran a full disk walk on the host. Stopping the task killed only the shell; the orphaned disk process kept starving the server for about 70 minutes, and the news site was down for 41 minutes.

This one went wrong. See what happened before you try it.
Show 10 more

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.