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.
Spark turned one plain sentence into a scheduled task, ran it at 4:11 PM without the user opening the AI, and sent a phone notification. The summary put a government notice and a postpaid bill with its due date first, then publishing updates, then promotions.
Every month the family benefits system asks him for a fresh proof of domicile, and a forgotten upload stops the payments. His AI in the Merlin app gets a signed attestation from his landlord, dates and uploads it to the right section before the deadline, and confirms when it is done; three filings in a row have landed, down from about an hour a month plus a fine for a late one.
He is juggling several legal cases of his own, and his lawyers do not have time to answer him every day. The AI transcribes audio, organizes his evidence and writes the case summaries he hands to them. He calls it the best tool he has ever had, and says stopping would mean going back to doing all of that alone.
He runs his email agent on a 2018 computer he already owned. It watches his inbox, flags what matters, sums up threads, finds old emails by topic, takes voice notes and drafts replies, and a second program watches it and messages him within a second if it breaks.
This only partly worked. Worth knowing before you try it.
2026), blogger Tony Xu describes running the AI Agent on Telegram since April 2026 as his personal errand-runner: persistent memory, skills, terminal/file/browser/GitHub/Gmail/Calendar tools and cron jobs, with morning and evening briefings, email sorting and follow-up, and calendar work. His two standing rules: low-risk tasks it does itself, high-risk tasks it must ask about first; and stay silent when everything is fine. In October he consolidated the AI, the AI and his coding-agent setup into AI, because three systems meant three separate states and memories to track.
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.
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.
Hemant Kadam, demonstrating his 'craziest use case' after a couple of days on the AI, opened the app to a Sarvam DevOps Engineer application page. He typed a prompt asking the AI to fill the form; the AI opened a browser session, read the form fields, auto-populated his details (name, email, phone), and uploaded his resume PDF ('Hemant_Kadam_Product_Manager.pdf').
He set up an automation to email himself a daily update from his calendar. Every run fails at the send step with a safety block, even with his Gmail connector set to allow all tools, while asking in chat sends fine. He rebuilt it several ways and every version stops at the same point.
This one went wrong. See what happened before you try it.