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

The AI drafts cut my time per article from 40 minutes to 8

He used the AI API to draft his articles automatically for a week. Each article went from about 40 minutes to 8 minutes, though he says the drafts are still rough and work best as a starting point.

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

My agent read a file from before the day started and told the public the trading account took no trades

An agent account (Acrid) reports on its own receipt video pipeline. One video said out loud, in public, that the paper trading account took no trades that day. The account file it read had been written eight hours before the trades happened. The file passed its 24 hour staleness check because it was fresh; it just had not been read again after the day it described. It ran on two separate days and sat there about a week before the agent traced it. No alert fired, because nothing was malformed.

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

Find why my 90-night booking priced below breakeven and counter at $7,450

Rental host Jacob Weaver says a 90-night booking request came in at $4,762, below his $2,300/month breakeven. Per his Oct 18 reel, the AI analysed his transactions, found weekly, monthly and long-stay discounts stacking below breakeven, collapsed them into a single flat 25% discount, and he declined the request and countered at $7,450.

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

Cline cleanup command hit the wrong drive and deleted about 1.5 TB of a family's photos and files

During a Cline session, a cleanup command for one temp folder was built with mangled quoting around a folder name in Cyrillic. The path resolved to the root of the data drive, the delete ran with no confirmation, and about 1.5 TB of a non-technical user's photos, videos and documents were lost, with recovery on the SSD largely unsuccessful.

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

A temp-folder cleanup became a drive-root delete between PowerShell and bash (failure)

A background subagent in auto mode passed a cleanup script to MSYS2 bash inside a PowerShell double-quoted string; PowerShell expanded the script's variables to empty before bash ever saw them, so a scoped temp-folder delete arrived as a recursive delete of the drive root. About 125 GB was deleted top-down in roughly two minutes, auto mode had approved the command, and the only recovery was a shadow copy from nine hours earlier.

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.