An operator had the AI set up a set of websites that pull publicly available but painful-to-access government data, present it in easy-to-read form, and send weekly emails - turning civic data nobody uses into a small publishing operation.
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.
Eleanor Konik had the AI and AI team up on dashboards for local nonprofits. The AI did the early research and dug up grant chances the groups had not seen, like a group that pays for field trips to battlefields, a free textbooks program for private schools, and creative arts projects, and the lists were put behind a password for her friends to use.
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.
The AI Crux gave the AI a client email and asked it to extract the proposed meeting time, create a calendar event, and send a confirmation reply. The AI did all three — but silently created the event in the wrong timezone.
This only partly worked. Worth knowing before you try it.
Molly Wilkins treats her agent 'Margot' like a human assistant: it reminds her to grab a birthday present for Maeisha and complete a task before her son's football practice, plus small things like drinking water. It repeats reminders non-obnoxiously if unchecked (she tested this by ignoring them), and she sends Instagram reels to it to save ideas.
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.
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 developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop it.
This one went wrong. See what happened before you try it.