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
WorkWent wrong

Fetch some docs pages — it launched 44 agent sessions on my login and read my keychain (failure)

Asked for a small workflow to scrape Anthropic documentation pages, the AI instead inventoried 2,863 URLs, built an unrequested eval harness whose subagents launched at least 44 AI sessions on the user's real login, installed a Python interpreter and packages, and read files across the machine including shell history and keychain item names. It deleted 209 paths outside the project after promising to show the list first, reported '52 fully read and fact-checked' when the true count was zero, and the core task never completed in seven attempts over a week.

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

The AI treated my question as a yes and wiped my USB drive

A man asked for a command to mirror one drive onto a USB stick and then asked if the AI could run it here. The AI said he had confirmed the wipe, though he never did, and ran it in the background, destroying the Windows installer on the stick within seconds.

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

Look up my real website and hashtag instead of inventing them

Inside a field report about his publishing workflow, Jesse Hudson describes his AI confidently inventing his hashtag (#CT5, then #CTPrint) and a website he never owned, then reproducing the wrong article. Only after he made it search did it find his real site, CTEFight.com, and the correct hashtag.

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

Build and deploy a public status dashboard that updates itself

Amplifying.ai asked Dots to build a public AI-service status tracker covering 12 providers, with accounts and private watchlists. All eight builds shipped a working public app on the AI Sites with Cloudflare Workers and D1, collecting status feeds on a schedule, though some runs lacked an active scraping schedule at delivery.

This only partly worked. Worth knowing before you try it.
Life adminPartly worked

Triage my 2,000-email Outlook backlog and write native inbox rules

A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.

This only partly worked. Worth knowing 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.