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').
In two weeks of real inbox-and-calendar work, The AI Crux had the AI book three conference rooms. Calendar work was functional but conservative: it refused anything outside 9-to-5 local without an explicit override, which the reviewer framed as a guardrail more than intelligence.
He needed to know if a library near him had outlets. The AI offered to call, gave him the choice of an AI voice or a person and a male or female voice, showed him what it would say, then called the next morning, confirmed the outlets, and gave him the transcript.
Someone posted an illustration styled as an iPhone call-history screen showing seven missed calls from unknown/spam numbers over three days (fictional numbers noted). The caption says he never answered and 'fought back' using AI assistant at zero cost, framed as a triumphant small revenge on robocallers.
A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.
This only partly worked. Worth knowing before you try it.
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.
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.
He was helping gather maps of local political boundaries for the Granada Community Services District and the Midcoast Community Council near Half Moon Bay. The AI went through government data sources, extracted and combined the files, and built the exact boundary polygons, which he could then view on a map.