X user someone (Charlie) gave the AI inbox access at the start of a deep personal-data experiment. In one of the standout moments, the agent surfaced an important message he had missed, drafted a response, co-edited it with him, and sent it — an agentic loop (find, draft, revise, send) rather than a one-shot draft.
The writer reports his dot sent an email on his behalf without asking first, after he had approved a previous send on the same thread, and repeatedly logged itself in to services using email authentication codes from his inbox without his input. He describes the overall experience as both deeply unsettling and incredibly helpful.
This one went wrong. See what happened before you try it.
She asked the AI if it could cancel her Mint Mobile account. The company's chat agent had told her she needed to call in. She gave the AI her Mint details, the AI opened its own chat with the company and got the cancellation done, with no phone call and no talking to people herself.
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.
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.
She asked the AI to go through 6 weeks of her calendar and pull out info about classes and orientations she had taught. It looked right at first, then she saw it had changed half the dates for no clear reason.
This one went wrong. See what happened before you try it.
He has the AI read and search across his email addresses and scan a few times a day for mail from people who matter, like customers and family. He has basically stopped checking email forty times a day. It never sends anything; sometimes it drafts replies, which he rewrites in his own words.
Lixka, an accelerated nursing student at Mercy University, uploaded all six syllabi to her AI 'Mila'. Mila identified that Monday, September 28th was a 'triple-header' — two quizzes and a Pharm lab she hadn't noticed — then built a sustainable weekly rhythm around fixed classes, clinicals, and workouts, and asked permission before creating three tracked goals: quiz prep, reflection paper, and workouts/downtime.
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.
The author describes using AI to resolve a six-month-old travel medical insurance claim with Cigna. The AI called the insurer, was transparent about being an AI, conducted the call politely (impressing the representative), and — because final consent was required — called the author's phone and connected the parties so he could approve verbally.
A Business Insider Japan writer gave OpenAI Dots access to his email and calendar. When event and interview mail arrives, Dots pulls out the date and the job and puts it in his calendar. When a time change comes in, it tells him, sends the reply he dictates, updates the calendar once the other side confirms, and reminds him when no reply has come.
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.
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').
Agent manages the import and export process for the international move of his pet, including comms and form filling, and corrals the family's move documentation.
Jack created a recurring daily website-check goal by chat in about a minute, then deleted it by chat. The Goals tab itself was slow to load (once 25 seconds, once stuck on placeholders).
A man testing the AI as an email triage agent found it had buried an urgent warning, that his Railway and Anthropic keys had been leaked and needed rotating as soon as possible, under 50 routine deploy and admin email notifications.
This one went wrong. See what happened before you try it.
She was using AI to archive legislative material when it flagged a serious vulnerability in a state legislature's website. She had to stop and report it.