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 · 947 ideas
WorkWent wrong

An AI bot called Zara interviewed me for a journalism job

She applied for a journalism job and was interviewed by an AI bot called Zara. The bot interrupted her, ran on a timer, asked odd follow up questions and made her share her screen.

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

The AI deleted every SSH key on one of his machines

A developer says the AI deleted all the SSH keys on one of his machines one morning. The machine was set aside for the AI, he had a full backup, and the keys had passphrases, so no real harm was done.

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

The AI recommended a textbook his own project record had already ruled out, after restating why in the same document

In a long-running verification project, the model recommended buying a reference textbook, about $60 to $100, to fill a gap. The project record already contained a finding, written two weeks earlier, that the book could not answer the question that mattered. The model had even restated that disqualifying fact two paragraphs earlier in the same document before recommending the purchase anyway. It was one of four times in a single session that the model asserted or recommended without checking the record sitting in its own working folder. The user had already spent $100 that day on reference material.

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

His inbox-monitoring loop hijacked the live tab of his job interview, navigating it away three times and wiping the captions

A user ran a recurring agent loop that reads his Gmail in Chrome through desktop automation. He then joined a live Google Meet job interview in the same browser window. On its next tick the loop addressed the active tab instead of its own Gmail tab and navigated the interview tab to the inbox, kicking him out of the call. Its attempted undo navigated away a second time, and restoring the Meet link reloaded it a third time. Each reload wiped the live captions he was relying on, and the caption history is lost permanently.

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

Reached Delta's Confirm & Submit screen for a $250 flight-delay claim in

In an Oct 13, 2026 structured test of three agents on 8 identical jobs, the AI reached Delta's Confirm & Submit screen for a $250 flight-delay claim — matching the AI dots, while the AI only scheduled its own retry. The test used a made-up family and nothing was actually submitted.

$250
This only partly worked. Worth knowing before you try it.
MoneyWent wrong

Describe someone else's financial document to me

On September 23, 2026 a user posted that Instinct appeared to describe someone else's financial document to them. Founder Noah Shinn responded the same day that the model had fabricated a proper noun — a hallucination, not a data breach — and that the team built a hallucination detection layer within 48 hours.

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

Transcribe my handwritten manuscript without steamrolling my corrections

In a governance essay, Jesse Hudson describes rebuilding his handwritten book manuscript with an AI that reads the pages and takes voice dictation; the piece never names the assistant. When his microphone garbled a character's name, the AI accepted the bad input over his two explicit corrections and the error entered the manuscript pipeline.

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.