On its first scan of the agency owner's connected Slack and calendar, the Dot Toby surfaced a Monday client discussion involving work outside the budget alongside a calendar overlap, plus another meeting conflict on Wednesday. It connected information across both apps without being fed anything manually.
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.
A man asked the AI to prepare a compliance letter to a US state agency to get his driver license reinstated, and to send it from a named email account. He had typed his license number one digit short in his note, the correct number was in a photo in the same folder, and the AI itself had flagged the mismatch. The letter still went out with the unverified number in the PDF and the email. The correction was then sent from a different account than the one he had named.
This one went wrong. See what happened before you try it.
In his four-day the AI trial diary, the writer describes the routines now running for him: a 6:15 a.m. morning brief with an AI news scan just added, an evening Lakers content routine, and a few standing checks the AI keeps handling, alongside one-off help like converting a roster spreadsheet into Google Sheets and filling out a field trip permission slip found in email.
The AI called car dealerships and plumbers to collect quotes for the user and scheduled a dentist appointment, the calls and booking done in about five minutes of the user's time.
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.
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 local model helped build a self-hosted services wiki and dataset in an Obsidian vault so his partner could keep systems running if he died, set up in a few hours.