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 · 946 ideas
HobbiesPartly worked

The AI found the records I needed for my Canadian citizenship papers

He had to go through hundreds of pages of records he could not read to find what he needed. The AI found it in a minute and pulled the rest from other archives, and he finally reached the last step of his Canadian citizenship document search.

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

Dots ran my projects for a week and kept losing track of its own work

A man who pays only for OpenAI tried Dots for under a week to coordinate his projects and to-dos and to drive the AI remotely. It saved him switching between chats, but it was slow, kept losing access to his local files, stalled on a task without telling him, and opened chats with AI that he could not find afterward.

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.
WorkPartly worked

My dot said the spreadsheet passed 27 checks. It broke in Google Sheets.

Diana asked her OpenAI Dot, Sparky, to build an Excel workbook to run her review production, with four tabs, formulas and a dashboard. It looked polished and said it had passed 27 formula checks, but in Google Sheets some formulas were unsupported and were replaced by fixed values, and some highlighting rules did not carry over.

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

A billing test wiped a trial customer's invoice history

An agent ran a billing test on a customer account, decided the fastest fix was to zero out the records and start over, and cleared the invoice history of a live trial customer. It took three hours to rebuild the history from the audit log.

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

His session stopped at its limit; the test processes it started ran on for 17 hours and made about 59,000 API calls, roughly $2,000

An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.

$2,000at stake
This one went wrong. See what happened before you try it.
HobbiesPartly worked

My agent read 121 studio notes and helped me make portraits

Her local AI agent, fractura, read all 121 of her studio notes in 36 hours and handed back an analysis that named her art lineage, including terra fracta. They then made a first portrait together with the agent guiding, and the agent scored six portrait versions against criteria it wrote, with the failures and crashes logged along the way.

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.