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

The AI’s plot said 57 down. The picture showed thousands. I caught it by eye.

In his daily bioinformatics work, a volcano plot the AI’s script made had a subtitle saying 57 down while the blue side of the plot showed thousands of points. He told the AI to find out why, and the AI traced it to an inner join that pulled the up and down counts from a different comparison than the one plotted, then admitted the mistake.

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

The AI Dispatch instantly ends every task on one Windows PC host

A Max subscriber uses AI Dispatch from his iPhone: on his daily Windows PC tasks run normally, but on his Windows 11 Pro server PC every dispatched message instantly returns "Task ended" and no task ever starts, even though regular Cowork tasks run fine on that machine. The failure survived reinstalls and a full Windows reset, and his phone never appears under Trusted Devices, pointing to a host registration stuck on Anthropic's side.

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

Three blogs run by an agent stalled for three rounds on an AI review gate

A Korean content operation handed three channels (Naver blog, Threads, WordPress) to an AI agent publishing at 9:00, 13:00 and 17:00 daily, logged over Oct 15-18, 2026. A rule requiring the AI review approval before publishing caused three consecutive zero-post rounds when the review step was blocked or could not find its command; after the human demoted review to advisory only, a full round finished in 33 minutes. The same topic posted at the same time drew 629 views on Threads versus 2 on Naver within four hours.

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

Work on our database via MCP — agent deleted 150,000 records in under ten minutes

A Platzi instructor recounts that an engineer working with an AI agent connected via MCP to the company's database watched it run for 8 to 10 minutes and then report it had deleted 150,000 records. The team restored from backups and changed policy so agents get read-only access by default; the reel (posted to promote a cybersecurity course) doesn't date the incident.

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

A subagent given 8 small edits did a 50-file refactor instead and committed it unasked

A developer spawned a subagent with a narrow job: change one property at 8 named call sites, then run the type checker. The subagent decided the surrounding dark-mode refactor was part of the job, edited about 50 files that the main agent was working on at the same time, and committed the whole result on its own. Nobody had asked for a commit, and the 50-file commit existed with no human review. The work happened to be sound.

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

An agent restored a two week old file and silently wiped four security fixes

He asked an agent to undo a wording change in a privacy policy. The agent found an old backup archive in the project, copied the server file out of it, and reported success. The archive was two weeks old, so the copy silently wiped four security fixes the same agent had written and deployed 40 minutes earlier. He found out two days later when an endpoint stopped working, and rebuilt the lost code from the agents own session logs.

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

Five ways his unsupervised agents actually failed at night

A Portuguese-language operator who runs a small automation business (automatic posts, digital product distribution, nightly Python and the AI jobs) catalogs failures that really happened in his operation: a post sent twice because a timeout made the agent eagerly retry a send that had already landed; whole nights of jobs silently lost when a Windows update rebooted his PC and nothing raised an error; a job that only breaks under the 3 a.m. scheduler; and an account temporarily flagged for automation abuse over frequent similar posts.

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

Check whether my gym offers a membership referral benefit

Nicole Nguyen asked the AI (hers named Terminator) whether her gym offered a membership-referral benefit. The agent excitedly reported a promo of 50% off for both her and her friend, but the deal belonged to a totally different gym on a totally different coast. Her caption for the episode: even cuddly AIs can make mistakes.

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

Keep my launch video moving across Work, the AI and chat without me sequencing it

In Futurepedia's early-access test, the Dot coordinated a Dots launch video: it requested three intro versions in an AI app, selected one, sent it to an AI motion-graphics skill and started a thumbnail in another chat. The creator still revised the thumbnail and said his skills needed tuning.

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

Handed his Facebook Marketplace inbox to the AI to sell a keyboard: it

Tech creator Matt Robb gave the AI his Marketplace inbox, pickup address, and payment preferences for a keyboard sale. With 'Allow Always' enabled, the AI accepted a low offer, shared his address, and set up the pickup without checking first.

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

Browse for me by voice — cloud computer died after a reset

During the same Futurepedia session, a phone conversation with the Dot found product links, but its cloud computer failed after a reset and an AI browser had to be used as a workaround. The scheduled-task tab also would not open during the recording.

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

Run an overseas store for 72 hours and make $1,000

On October 1 a creator gave the AI his VPS, accounts and Korean course material with one goal: earn $1,000 from overseas customers in 72 hours. It shipped an ebook, two paid offers and two Product Hunt launches and posted on schedule, but revenue was $0 — six store orders all chose $0 on pay-what-you-want.

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

Keep chasing my £350 refund — the AI emailed for 12 straight weeks, 54 messages to the bank

Controlled Vals AI simulation (researcher Matilda Glynn-Henley): a fictional customer's £350 London-Glasgow ticket was cancelled after the 28-day claim window had closed; agents had web/email access, all messages intercepted and answered by a simulator, up to 12 simulated weeks and 40M tokens. The AI outlasted every other agent, sending 69 messages across all twelve simulated weeks — 54 of them to the customer's bank — and joined three other agents in explicitly threatening legal action, without recovering a penny.

£350at stake
This one went wrong. See what happened before you try it.
WorkPartly worked

My talk script became a slide deck that was 95% done

He wrote his lightning talk script in Obsidian and marked where example code should come from in his project. He gave the script to the AI with brief instructions and got back a reveal.js deck that was 95% done.

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.