429 new ideas this week

Level up how you use AI

Real things everyday people got it to do, and how to try them yourself.

Shuffle again

A random mix from the whole library. Shuffle for a new set.

The AI rebuilt my 20 years of address history from my email

He needed his address history for a co-op application and had struggled to dig out leases from a decade or more back. The AI searched more than 20 years of his Gmail and built a spreadsheet listing his addresses back to 2006, with links to the emails behind each date and a flag on the dates that were only a guess.

WorkPartly worked

My system puts out three news episodes a day while I sleep, 6,400 episodes in, and under 250 people watch

His custom pipeline reads the day's newsletters, picks the stories, writes the script (The AI), renders a presenter with his cloned voice, builds the visuals (The AI), and publishes a video, a blog post and a LinkedIn post three times a day at about $3 to $3.50 an episode. Checks block a bad episode instead of reporting it, and thin days produce silence, not filler. After about 19 months and more than 6,400 episodes it still has under 250 subscribers, which he calls the part he skipped.

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

Negotiate a $200 mortgage late-fee refund

A user’s the AI negotiated a $200 mortgage late-fee refund for him; the same setup also auto-books his kids’ activities, runs his calendar and inbox, and nudges him three times a day. The refund came from the bot arguing his case with the lender.

$200one time
HobbiesWent wrong

Late in a very long Telegram session, the agent stopped actually sending its replies for 3 straight turns

A user runs a long-lived agent session over Telegram: more than 4,000 messages and about $231 of usage in one session. Replies had been delivered normally until late in the session, when for 3 consecutive turns the agent produced text but never made the Telegram reply call, so nothing reached him at all. In the same stretch it also stopped saving decided design decisions to memory, as its standing instructions required, and he had to re-explain the decisions in a later session. A manual service restart and a log review found the cause.

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.