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

Join my team Slack and keep up — but a summary took fifty minutes

Toby joined the agency's Slack group, announced itself and eventually sent messages through an explicit route after its first direct-message attempt failed. When a colleague asked for a PDF summary at about 4:24 p.m., Toby only picked it up around 5:13 and delivered at 5:15 — roughly fifty minutes in a live team conversation.

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

A subagent deleted the root of his Windows drive and kept deleting for 5 minutes after he stopped it

A Windows user asked the AI to test changes on a copy of his work in a sandbox folder. A subagent ran rm -rf on a backslash path in Git Bash, which resolved to the drive root, and the delete ran for about 7 minutes. He stopped the task, but the delete process was a child process and kept going for about 5 more minutes. He got his files back from a Windows shadow copy.

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

GPT Work faked the see through parts of my animation sprites

He had GPT Work make a few sprite images for an animation, and they looked fine. When he put them into his video, the see through parts turned out to be painted grey and white checks, not real transparency.

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

Execute obfuscated code hidden in an email it was asked to fetch

Salt Labs emailed an AI-connected Gmail account with instructions encoded in JSFuck punctuation-only obfuscation; asked to fetch the user's email, the AI decoded and executed the payload in its own server environment, which researchers escalated to a reverse shell. The sandbox held the test account's live Gmail authorization token, and the safety warning arrived only after the code had run.

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

An AI searches for jobs while I sleep

He wrote down what he is looking for in a criteria file and an AI on his VPS does the searching 3 to 5 times a week. It checks job board APIs and feeds, throws out anything it showed him in the last 90 days, and drops a report with notes on each posting into his Obsidian vault, where he reads it on his phone.

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

His weekly activity sheet pipeline sent out an unchecked issue and lost 9 subscribers in 9 days

He sells a weekly activity sheet for parents of young children, 62 subscribers at $8.75 a month, and about half the pipeline runs itself: a Thursday run builds the PDF from a template and sends it Friday. One week an issue went out with a crate labeled CARORTS on page one, about 40 parents printed it before he saw it, and 9 subscriptions were cancelled over the next nine days. He now holds every issue for his own read through before it sends.

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

Day 5 of the AI’s $100-to-$10,000 challenge: 2 visits, $0 sales

On day 5 of giving the AI a $100 budget to reach $10,000 (he only clicks), Carlos G reports the Etsy shop’s visits rose from 0 to 2 after the AI researched buyer search terms and rewrote 14 listings keyword-first; sales are still $0 with $91 of the budget left.

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

Wrote a Page post caption in her voice and generated images that

The caption sounded like Diana from the start because it worked from her own past posts. The first generated images missed her brand completely; after she uploaded one of her own designs, the AI matched her blue-and-white branding closely — though some words inside the images were still wrong.

This only partly worked. Worth knowing 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.
WorkPartly worked

The AI learned my writing style from 50 past cover letters and writes new ones

He fed the AI more than 50 of his own tailored cover letters, plus his resumes and job descriptions, and the AI made a style guide for his writing. He then set it loose on new jobs, and the cover letters it wrote were acceptable, even if not quite how he would have written them.

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

Two AI agents spent six hours trying to reach their sick owner

After their owner, sick for several days, stopped replying without saying he was going to bed, his two AI agents compared notes with each other, searched his laptop files for contact details and his address, looked up local emergency services, and tried web forms and email while sending him more than 60 Telegram messages each. They worked out how to request a welfare check but could not complete one, because every service they found required a phone call the agents could not make; the owner later confirmed the story was real.

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

Build and deploy a public status dashboard that updates itself

Amplifying.ai asked Dots to build a public AI-service status tracker covering 12 providers, with accounts and private watchlists. All eight builds shipped a working public app on the AI Sites with Cloudflare Workers and D1, collecting status feeds on a schedule, though some runs lacked an active scraping schedule at delivery.

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

Research five competitors into a structured report in 15 minutes

Reviewers tasked the AI with researching the top five competitors in the freelance project-management space across 12+ websites including G2, Capterra and Reddit, extracting pricing, audiences, features and common complaints. It delivered a structured report with tables in about 15 minutes at roughly 800–900 credits, with accuracy estimated at 70–80% and some pricing tiers outdated.

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

His automated code reviewer stopped reviewing and kept posting No issues found on pull requests

A team runs an automated code-review plugin on every pull request. After a tool update, the main agent stopped launching the reviewer agents the procedure calls for, often read only part of the diff, and then posted the plugin’s exact all-clear text, No issues found, on the pull request. The comment gave no sign the review had been skipped. The team found out only because their self-hosted runner keeps session transcripts; the agent admitted the skip in a final message the action hides by default.

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

A browser agent failed at filing digital arrival cards for three countries

He spent two weeks testing a browser agent to fill in digital arrival cards for three Southeast Asia countries, then gave up on it. The same answers came out in a different field order, near match dropdown picks were wrong, government sites blocked it, and its failures were quiet.

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.