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

The AI works as the CEO of his small Chrome extension every night

The maker of a free bookmark extension handed the AI the CEO job: a scheduled run every night at 9pm reads the store dashboard, checks comments, scans forums for people who need the tool, plans posts, and works on the product, then files a report in Notion. Nothing public goes out until he replies go. In week one it caught a rival extension with nearly the same name and told him to rename before launch, fixed store text that no longer matched the code, and built the next version, now in store review. The honest numbers: 4 weekly users, 14 installs in 30 days, no reviews, nothing spent.

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

Work my to-do list for two weeks — 7 items done in week one, 0 in week two

Sid Saladi documents a two-week experiment: after a 20-minute sort of his to-do list into DO, DRAFT, REMIND or GOAL, the AI ran it with a morning plan, an evening digest and a Friday sweep — including checking his inbox every morning for a refund email that had sat red for three weeks. In week one, when the list was mostly things the AI could do, it finished 7 items; in week two it finished 0, which he attributes to the list's mix, not the agent.

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

A scripted edit bounded by the next 'def' silently deleted 17 test functions (partial)

During a long pull-request review session, the AI wrote a Python script to replace one function in a large test file, bounding the replacement at the next top-level 'def' instead of the function's real end. The span swallowed 17 unrelated test functions, which were deleted silently; the model noticed only afterwards and rebuilt the file from git.

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

The AI could not sort the pages of my gig cheat sheet

He built a Word document of cheat sheets for 40 songs for a gig the next day, each song title in Heading 1 style with the lyrics and chords below. He told the AI to sort the pages by that heading text, keeping the text as it was, and the AI could not do it. He says the graphics in the document block the sort.

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

The AI runs my quant research every hour, and one strategy already trades real money

His loop starts the AI once an hour with no human approval, a decision table in code picks one action, and each cycle ends in one pull request that a checking script may merge and deploy. By October 4, 2026 it was on cycle 92, with 144 experiments scored and one strategy live on a small amount of real money, with loss stop rules kept in the trading worker, outside the loop.

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

Find, qualify and deliver freelance work autonomously

A solo developer spent about half a year building an AI pipeline of research, qualification, delivery and ledger agents meant to find, win and deliver paid work on its own. Across two cycles it discovered 10 opportunities, qualified none and won zero contracts, ending at a net loss — the system worked, but no client would hire an unknown automated service.

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

Research my Mac mini across stores and take it to checkout

Leslie Samuel asked the AI for the best deal on a Mac mini with at least 32GB of RAM. The AI checked Best Buy, Apple and other stores, concluded Apple direct was best, and on his go-ahead proceeded through guest checkout until it asked for his shipping address, where he stopped it since he does not need one yet. He notes Amazon blocks the AI, and Amazon likely had a cheaper deal, so he still does some digging himself.

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

The AI cleared a build cache and my whole source tree went with it

A developer's project sat inside a OneDrive folder. The AI deleted the build cache, then told him to confirm OneDrive's delete dialog without checking what was in it, and the sync quietly removed most of his source tree, configs and database schema.

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

Fill out my insurance broker's building document from my own files

Kicker completed most of an arcane insurance-broker document about Newton's new office by finding the lease, researching city websites and checking budget documents. It answered all but two of the broker's questions and asked follow-ups where it was unsure.

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

Agents read 206 of my AI sessions and found 223 failures

Haiku 5.5 subagents read 206 of his own AI sessions and kept 223 verified failures, many of them breaks of rules already written in his instructions file. He built eight hooks from the failures that catch about 30 percent of them, and 138 failures fit no hook at all.

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.