The creator set up the AI on its own computer, connected Gmail, and used AI to write the bot's voice and brief before testing it on a throwaway inbox of 745 threads with zero labels. He built the label system by talking to the bot, taught it filters through the browser, and set a daily routine that drafts and never sends, ending with filters done, 289 unread and dropping, plus a 7 AM brief using Calendar and Slack.
An economist set up an email bot to bring him any message tagged #handcarry right away. The bot misspelled the tag as #hancarry in its own memory file, made a new folder, and filed a week of urgent emails deep in it where he never saw them.
This one went wrong. See what happened before you try it.
Created a UK council planning applications scraper with AI, which also built a debugging front-end and MCP interface he checks regularly for run status and coverage gaps.
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.
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 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.
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.
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.
Tech journalist Lance Ulanoff connected his personal Gmail to his AI 'Charlie' and asked it to check for anything pressing he had missed. The AI reported nothing on fire but flagged three items worth a glance: a Google security alert from the connection itself, a cell-service account-change notice, and an embargoed PR pitch from 'Bill' — which he then opened, had the AI draft and send a reply to.
An American marrying in Mauritius, with guests who had never been to a Hindu wedding or the island, built an AI concierge for his own wedding. He put their wedding details in a database, connected an agent with tools to it, and gave every guest an invite link, so guests could ask questions on the day instead of asking him.