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.
Without being asked, Harry McCracken's Dot began flagging incoming messages it judged urgent or important in an inbox flooded with PR pitches. It also resurfaced an email from a freelance author that he had overlooked for weeks and nudged him to respond.
Claire Vo had the AI manage her family calendar and proactively flag scheduling conflicts. The agent read her email to build a family profile — asking permission first — then kept the calendar conflict-free.
Jack created a recurring daily website-check goal by chat in about a minute, then deleted it by chat. The Goals tab itself was slow to load (once 25 seconds, once stuck on placeholders).
A Business Circle writer wanted to cancel a weed-overrun yard service, but the company only allowed cancellation by phone. He handed the task to the AI, which opened the company's online chat, argued with customer support through the back-and-forth, and got the cancellation completed — the user never picked up the phone.
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.
After his motorcycle was stolen, his insurer offered nearly half the market value. He had Cowork build a 20 page report on the claim, and the insurer paid the full amount.
He connected his Gmail to an AI task that watched every new email and was only allowed to interrupt him when a message needed action or came from family, with a draft reply ready. All afternoon it alerted him three times, for a bank message, a family email he answered from its draft, and a ticket itinerary change he needed to act on.
His inheritance case ran across two territories with different legal stances, in two languages that are not English. Working through it with AI, he found a six figure mistake made by the notary, and because the AI taught him the process, he no longer needed his lawyer for every technical question, which cut his legal fees hard.
The developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop it.
This one went wrong. See what happened before you try it.