Rachel D. Gainsbrugh (someone, ~3.5K followers, AI/systems creator) signed up for the AI on Sept 13, 2026, connected her calendar read-only, and typed six standing errand rules once — including a 7:05 AM daily calendar scan that flags overlapping meetings or ones falling inside a flight — then handed it two long-dodged errands (an appointment blocked by a flight, a subscription update).
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.
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.
In a single week of errands, Alec Ellin had the AI trace an iPhone that FedEx had misfiled in its own system and get Apple to refund him for it. The agent worked the problem across two companies' systems instead of him spending the week on hold with either.
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.
This one went wrong. See what happened before you try it.
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 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.
He got the AI to build out a structured dataset of all 4,925 vacancies, with job titles, organisation, salary and location. He shared it in a spreadsheet for other people to play with.