He pasted one prompt into AI, and the AI read the Carly email setup docs itself, finished the signup, and took the verification code. The inbox, named Loopy, now takes tasks by email and asks before replying to anyone outside.
Agency owner Rui Fu (someone, 253K followers) demonstrates the daily system he shows for the AI: an 8 AM scan of the last 24 hours of Instagram DMs, categorised into brand partnerships, collaboration requests, fan messages and spam so he wakes up to only the important ones. The tutorial also shows an auto-reply rule for guide inquiries and offers his prompt guide in exchange for comments.
Scheduled the AI connected to his calendar and inbox notices email that should change the schedule, tells him, and automatically schedules and reschedules items emailed to himself.
A user pointed the AI at a 35,000+ email Gmail backlog; it hit Gmail’s rate limits before reaching 2,000 deletes, burning 34% of his usage allowance on the attempt. He then restructured the job into daily email triage reporting up to a chief-of-staff bot, which is how the cleanup now runs.
This only partly worked. Worth knowing before you try it.
He uploads his own data and points the AI to specific sources and documents, with examples he made before to show the format he wants. The AI then builds the tables and graphics for his Education Rights Project, public pages on education rights and funding in US states, with policy briefs, slide decks and interactive widgets.
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.
Tetsuro Miyatake had the AI call Volvo Cars as 'Hailey' on Matt Schlicht's behalf to check routine-maintenance availability for his XC90. The service department had openings all the following week starting Monday at 8 a.m.; the AI clarified it was checking availability only, not booking, since a phone number was still needed.
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.