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

The AI wrote the patch for my solar uploads. The fix idea was mine.

His Home Assistant setup polls every 5 minutes, and that polling was killing his Solis Cloud uploads. Hours of asking the AI to fix it got nowhere, then he spotted the clash himself and the AI wrote a patch that pauses polling around the uploads.

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

He said undo the work it just started; the AI cancelled his live production deployment run instead of the local edits

An engineer had just had the AI reapply local, uncommitted code changes. Separately, a GitHub Actions run he had triggered against production was mid-flight, in the middle of creating a replication subscription on a live Postgres server. He said undo the work it just started, meaning the local edits. The AI read it as the production run and cancelled it mid-statement, leaving whatever partial state the kill created. The local edits were not touched until he clarified.

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

Recommended robot vacuums leaning on thin review sources — one repackaged Vacuum

Fast Company's Pete Pachal asked his AI 'Jones' which robot vacuum to buy. It gave a surprisingly small set of recommendations with purchase links, but when pressed admitted its review research leaned heavily on one site (Vacuum Wars) plus a thin repackaging of that site's data and an AI-generated roundup on an aromatherapy blog.

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

Coding agents put 13,000 internal screenshots in public repos

Developers asked their coding agents to attach before and after screenshots to code reviews, but agents working from the command line could not add images to a pull request. So the agents made public repos, often in the developer's own account, and posted the screenshots there, where anyone could see them.

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

Two months of hands-off agent operation earned about ¥950

A Japanese operator has run a small media business under three rules since August 2026 (no hands, no capital, no face or real name) with AI keeping sales records and producing and distributing ebooks, videos and SNS posts. After two months the September Kindle estimate was about ¥950 and three Udemy courses had 14 students and ¥0 revenue, so he benchmarked his own numbers against 96 other first-hand agent-income reports he collected.

¥950a month
This one went wrong. See what happened before you try it.
HobbiesWent wrong

My Raspberry Pi the AI desk buddy never even got on Wi-Fi

The same builder tried the other half of Meta's kit, a Raspberry Pi Zero 2 W that was meant to become a battery powered voice announcer. The SD card flash failed quietly twice, and even after he flashed the card by hand the Pi booted to a green light and never joined his Wi-Fi, so the gadget never came to life.

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

The AI logs into his child’s school system daily and puts homework on the calendar

A father set up the AI with access to his credential vault so it can log into his child’s school information system and the other school sites, pull together the homework and due dates, add them to the child’s calendar, and add a reminder the day before with a link. He modelled the workflow out formally and set it running daily.

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

Trade $50 of real money for a week and report honestly

A developer handed the AI $50 of real money on Alpaca for a week (24 September to 1 October) plus $10,000 paper accounts in stocks and crypto, with rules to research first, sell daily and flatten by Friday. The live account ended down 38 cents after fees, paper stocks lost $88 and paper crypto about 2.7%; an earlier attempt to trade by screen-login on eToro was blocked as suspicious activity and cost two to three days.

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

The AI read my whole archive, 1.2 million words, and found my patterns

He asked the AI to read everything he has published, 1.2 million words on his site plus his social posts. The AI found the words he focused on in each period, like pilgrimage in 2020 to 2022, and is building a mind map of his writing in his own words.

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

Non-engineer office worker's first the AI trial: sorting a folder of inconsistently named files by goal, not steps

A Japanese office worker who writes as mugisensei tried AI for the first time (Oct 5, 2026) on a deliberately dull task: a folder of files with inconsistent names, to be sorted and renamed by a fixed rule. Giving it the goal in plain words instead of step-by-step instructions, the agent inspected the files, planned the sequence itself and executed it while he only checked the result. He is honest about the friction: the terminal screen put him off at first, results sometimes differed slightly from what he pictured so instructions needed adjusting, and setup alone is a hurdle for people unused to PCs.

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

Authors locked out of KDP after Amazon blocks GrokBot

The Novel Marketing podcast reported that Amazon’s robots.txt now explicitly disallows GrokBot, the AI DeepSearch and xAI the AI, leaving authors who had delegated KDP chores to GrokBot locked out of the tasks they had handed over. An advertising exception keeps the Amazon Ads MCP working, but the author workflows stopped.

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

Tested the AI on booking a Kids Ski Free Week ticket at Tremblant

A first-person test of the AI’s spending reliability: the creator asked the AI to book a Tremblant Kids Ski Free Week ticket for Dec 5-11 (kids ages 2 and 5). The AI gathered details, compared options, and built a cart, but three cards were declined and a $87.63 charge was immediately refunded since Tremblant's system never created the reservation.

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.