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.
Around Elmira and Corning, New York, event listings were scattered across library systems, a brewery site, a school app, chamber newsletters and Facebook, so people found out about things the day after. He had the AI build one page that checks 101 sources across three New York counties and part of northern Pennsylvania: 1,855 listings over the next 90 days, 1,767 events after duplicates are merged, about 250 in any week, at 159 venues. A cron job reruns it every six hours on cheap shared hosting, about 8,300 lines of PHP, and cancellations mostly handle themselves because an event disappears when its source stops listing it.
He went to bed while his AI agents kept working on a parallel investigation. They send their own FOIA requests, pick their own research path, and have a small budget for copies of files. He set the web permissions for the night before letting them loose.
This only partly worked. Worth knowing before you try it.
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.
Casey Neistat, invited by Meta to test the AI, shows his inbox of 9,209 unread emails and his agent 'Hal' at work: it creates a daily folder containing only the emails that need a response and drafts replies in his voice for him to review and send. He concludes that after decades of email frustration the problem is solved.
The road to a takeoff spot they fly from was not on OpenStreetMap, though satellite images showed the track. They built a tool called osmctl, and the AI drove it and mapped the road.
He follows the CNN lawsuit over White House press briefing access. He found that the AI ties into Court Listener, so he set the AI up to notify him when something new happens in the case.
This only partly worked. Worth knowing before you try it.
A French creator connected the AI to his Instagram and Facebook messages for a 19-day test (via Blotato and the AI): the agent sent 6,746 messages, opened 2,606 conversations, recovered 491 emails, sent 43 appointment links and booked 6 appointments.
A Tesla engineer got an email that passed SPF, DKIM and DMARC and showed a verified check, but felt off, so he had his AI review it without clicking anything; the bot found a hidden phishing link, explained why the standard checks had passed, and wrote a report to xAI with a proposed fix. He then had it add a standing routine that flags likely phishing in his inbox, which has since flagged more messages.