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.
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.
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.
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.
He had the AI collect his will and trust documents and check them against state statutes. The review found missing signatures, an illegal clause, and outdated law references, and he fired his attorney the same day.
TechMitra founder Ayush Singhal asked the AI to triage his Gmail thread by thread. It proposed archiving ten promotional emails, correctly found nothing to do on other categories, and unprompted flagged a spam comment on his second website. After his approval it archived nine FYI threads and left two genuine action items.
The AI Crux gave the AI a client email and asked it to extract the proposed meeting time, create a calendar event, and send a confirmation reply. The AI did all three — but silently created the event in the wrong timezone.
This only partly worked. Worth knowing before you try it.
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.
He runs AI on his homelab. He can ask the AI to throw an event on his calendar and it appears, and the setup can also send events to his primary calendar by email.
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').