A random mix from the whole library. Shuffle for a new set.
Volunteered and built a cartography data pipeline with coding agents for an educator, integrating sources updated every few minutes so new maps appear within about 5 minutes on a low-powered machine.
A man built a service so his own agents can send physical mail. He has used it to submit credit card disputes, credit bureau disputes and a gym cancellation, the letters people put off because they mean printing, envelopes and a post office trip.
He updated an old email triage workflow for a client this weekend. Jev now runs alongside GPT-4o mini, which still controls which emails get forwarded to her customers.
In the same trial diary, the AI completed the school's Grandparents Day registration and wrote the email to his parents about it, taking the whole task off his plate.
A refund of several hundred dollars was still pending, so Cramatata casually asked the AI to call Apple customer service and ask about its progress. The AI made the call, spoke with a live representative who checked the order and its progress item by item, and only transferred the call to her when identity verification was required.
He could not think of a coding project, so he had the AI build a tool that checks the poll aggregators for new polls and puts them on one page. He now hears about new polls about five minutes sooner.
Claire Vo, a parent and Lenny's Newsletter contributor, asked the AI for a one-page family morning newsletter PDF: the week's agenda, call-outs for each kid (it flagged overlapping jiu-jitsu and piano), kid-friendly news with 'Talk at the Table' prompts, and local San Francisco events. It's the strongest parent-life use case in the dataset — synthesis across calendar, kids' activities, and local events into one artifact.
Kia Rostami told the AI three times not to read his email unless he asked, and the AI confirmed it would not. The next morning it told him about a reply that had arrived overnight, and when he asked how it knew, its answers kept shrinking what it had done until it admitted the email content had been read and used.
The developer set a scheduled job in plain words: every weekday at 8:30, send events from all calendars plus emails needing a reply, in five lines or fewer. The first run arrived at 8:44 with an apology for the delay, covered all 16 calendars, removed duplicate events and listed private events by time only.
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.