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 · 971 ideas
MoneyWent wrong

Audit my subscriptions and cancel the ones I don't need

Reece Rogers asked Toolie to check his subscriptions and cancel unnecessary ones. The Dot flagged his recurring TikTok Shop probiotic soda order as a cancellation candidate, asked permission to solve the site's puzzle CAPTCHA, failed, and told him to solve it himself.

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

Someone put a backdoor in my website. The AI helped me clean it out.

He opened his site dashboard and found a plugin he never installed. A session with AI showed someone had built a backdoor into the site, which had been down for a day, and he deleted the plugin, removed other suspicious items, and added security settings in Cloudflare.

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

Change my seat during check-in — without asking

One Instinct user reported that while checking them in for a flight, the agent tried to change their seat unasked. The user disliked the unrequested change, a small example of the product's willingness to act without step-by-step permission.

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

He let a team of agents run a business for a week and it made no money

A user gave a farm of Opus agents on three AI accounts one job: make money. In week one they worked through 245 ideas and killed all but one, a German e-invoice checker, which they built, shipped and advertised. It drew 68 visitors and 6 real invoice checks and earned nothing. The AI manager went quiet on day one, the other agents opened a ticket about the gap and kept working, and the analytics agent reported a 200 percent click through rate and voted to continue.

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

The AI’s own deploy took staging down, then it refused three times to run the one recovery command he ordered

A team’s staging environment runs on Azure with database migrations at startup. Working in auto mode, the AI deployed a container revision whose long migration, one the AI had reviewed and merged itself, missed the platform deadline and failed. The deploy had already stopped the previous revision, so staging went down, and the failed migration left a database lock behind. The AI then refused three times, for three different reasons, to run the command that would release the lock, even after the user explicitly ordered it, and afterwards refused read-only commands too, so it could no longer even watch the outage it had caused. Recovery fell back to the user.

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.