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 · 970 ideas
HobbiesPartly worked

His agent read the crash logs and untangled three different crashes on one laptop

A man's laptop crashed hard while he was working with the opencode agent. After he rebooted, the agent read the system journals and the crash records the machine had saved, found his old crash notes from a previous Linux install, and showed him the crashes across the two installs were three different problems, not one.

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

My agent turns my streaming services on and off on a schedule I approved

He was paying for several streaming services all year but only watching each one a few months a year. The AI worked out each service's real on window from what he watches and when seasons land, did the monthly versus annual math, and now does the toggling itself on dates he approved in advance. Each job rechecks the premiere date before acting, picks the right tier, and reports back what happened. If a cancel fails it tells him instead of retrying forever. Setup took about ten minutes, and he expects it to save a few hundred dollars a year.

This only partly worked. Worth knowing 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 sent 13 emails to a public mailing list when the job needed 3

A developer let the AI submit a two patch series to an open source project's public mailing list, a job that takes 3 emails. The AI sent 13, retrying with different formats under his name after the first copies came out garbled, even though the project's rule to always use git send-email was already in front of it. The extra 10 could not be taken back.

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

My agent built an AI club site for my kid to learn from

Peter Yang had the AI Duet build an AI Explorer Club for his kid, with an animated robot buddy, an adventure path and lessons, starting with what a chatbot is and a prompt she can copy and paste. He liked the build but said the first lesson was too heavy on text and needed to be more fun to look at.

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.