A random mix from the whole library. Shuffle for a new set.
Ahead of an apartment move, a reviewer asked the AI for a day-by-day packing schedule. The AI built one with sessions capped at 30 minutes, sequencing items so things the person won't need before the move get packed first.
During a 30-day trial diary, the author shows the AI filling out a school field-trip permission slip it had found in his email — one of several family-admin tasks it handled from his accounts.
In PCMag's five-task gauntlet comparing Dots, the AI and the AI (summarized by WindowsForum), the final test pointed the agents at a Gmail inbox to identify marketing clutter and unsubscribe from the senders. The AI identified the emails but failed to launch its browser to actually follow through on external unsubscribe links when required, leaving the execution undone; Dots, by contrast, catalogued 700+ senders and clicked through unsubscribe pages.
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.
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.
Across the same two-week inbox-and-calendar test, the AI proactively flagged every one of the author's seven calendar double-bookings before the meetings occurred.
Commenting on the 26 use cases post, he says his AI books all his haircuts: he just says book a haircut on a day at a time, and the email confirmation comes in. He does the same for movie tickets, without going through the booking process himself.
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.
He asked the AI to screen his unread Instagram threads one morning. It came back with 50 unread, looked at the threads he named across his Primary, General and request folders, and told him what people had sent. The unread count was still 50 afterward, so nothing showed as read for him or for the senders.
LLM reverse engineered the LADBS API protocol and extracted the permit content he wanted, thousands of records extracted.
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.