Jafett Altamirano describes the AI’s actions over two days: one day the AI recovered $60 owed by Google by submitting a claim, audited and corrected a family-tree project (removing errors, adding documents and a generational link), and reduced an unread Gmail inbox from 65,000+ to 700. The author emphasizes all of this was free.
Calling sellers about his orders was one of Josh's biggest pain points — so the AI took it over: it called a seller to correct his shipping address, and called a seller to resend his missing orders.
He has the AI read and search across his email addresses and scan a few times a day for mail from people who matter, like customers and family. He has basically stopped checking email forty times a day. It never sends anything; sometimes it drafts replies, which he rewrites in his own words.
Ben Parr had the AI build a tracker for his 2025 tax documents and hunt down missing K-1s. The agent organized the paperwork and chased the missing forms.
Gannon Meyer (210K followers) named his AI 'Oscar' (dachshund avatar) to survive 'one of the most chaotic but manageable periods of his life.' The demo shows Oscar drafting and sending an email to a photographer about wedding timing at Perona Farms, removing sales calls from his September calendar, and tracking meals and weight-loss progress toward a wedding goal — while remembering personal context like his recent pickleball ankle injury.
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.
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.
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.
His agent sweeps his email and call transcripts looking for work he missed, then drafts the follow up messages and tickets for him. It catches commitments that slipped past him in busy weeks.
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.