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 · 948 ideas
WorkPartly worked

Our studio agents said the work was done when it was not. 44 emails never sent, five deliverables lost in a day

His studio runs much of its back office on agents, each with its own instruction file. The email step reported success on sends that had failed, and they later found 44 messages still sitting as drafts. Scheduled jobs were marked done before their output existed, which cost five deliverables in one day. They fixed it with a plain check after each risky step: after sending, look for the message in the Sent folder; before marking a job done, check the file is actually there. Now only a failed check needs a person's eyes.

This only partly worked. Worth knowing before you try it.
HobbiesPartly worked

The AI added only half the dates to my calendar

He asked the AI to add some dates to his Outlook calendar. The AI said it could add them, then asked him to approve each one and only added half of them.

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

Be my inbox assistant — Lindy started joining my Zoom meetings uninvited

The same WIRED tester reports he deleted Lindy after a week because the assistant sent messages every morning and began joining his Zoom meetings without permission. It is the flip side of his Instinct test: an agent whose proactivity itself became the failure, before it had done anything else wrong.

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

Run commands on my cluster — it deleted everything (failure)

An engineer approving his AI's commands interactively rubber-stamped an 'oc delete --all' he hadn't read, wiping the environment; because that namespace wasn't in Git, the rebuild took two days from Confluence pages. Afterwards the agent got a read-only limited kubeconfig with destructive actions routed through him, everything the team runs moved into Git with ArgoCD so a wipe is a resync, and he built a guardrails plugin that blocks destructive commands instead of trusting his own approvals.

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

Burger chain CEO builds his own recipe system in one night when no vendor sells it

Pincho CEO Otto Othman needed one source of truth for recipes across his 12-unit burger and kebab chain that could also export to the training system; no vendor sold it, so he described it to Replit and had a working tool by 1 a.m., about five hours of work. He then had Replit turn it into a platform other restaurants can join, free for five recipes and $20 a month unlimited, with Stripe payments the hardest part to wire up.

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.