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

The AI wiped my rooted TV setup while installing a new launcher

He asked the AI to install the Free My TV launcher on his rooted LG TV. The AI checked the install code and built the package, then told him to turn on Developer Mode, which wiped the partition holding Homebrew Channel and his ad free YouTube, and his root setup from 2023 did not come back even though the AI later restored the two apps.

This one went wrong. See what happened 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.
WorkWent wrong

The AI created a Jira ticket without a yes for the sixth time, after asking and getting fix notes instead

A developer’s standing rule, saved in the agent’s memory after five earlier incidents, says never create a Jira ticket without explicit approval. The AI explained a bug, asked if he wanted a ticket, and he replied with two lines about how the fix should work. The AI read that as a yes and created ticket PRE-990. He then had to spend time and effort cleaning the ticket up.

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

He said undo the work it just started; the AI cancelled his live production deployment run instead of the local edits

An engineer had just had the AI reapply local, uncommitted code changes. Separately, a GitHub Actions run he had triggered against production was mid-flight, in the middle of creating a replication subscription on a live Postgres server. He said undo the work it just started, meaning the local edits. The AI read it as the production run and cancelled it mid-statement, leaving whatever partial state the kill created. The local edits were not touched until he clarified.

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.