Outside code, his biggest win is boring paperwork. The AI filed his reserve duty refunds, sorted out his national insurance payments and did his flight check-ins, working in his own logged in Chrome. Each job is about ten minutes of work, which is exactly why he kept putting them off. He gives each area of his life its own folder with a CLAUDE.md and a notes file, so the money stuff does not mix with the rest.
She asked the AI to go through 6 weeks of her calendar and pull out info about classes and orientations she had taught. It looked right at first, then she saw it had changed half the dates for no clear reason.
This one went wrong. See what happened before you try it.
The author describes using AI to resolve a six-month-old travel medical insurance claim with Cigna. The AI called the insurer, was transparent about being an AI, conducted the call politely (impressing the representative), and — because final consent was required — called the author's phone and connected the parties so he could approve verbally.
He connected his Gmail to an AI task that watched every new email and was only allowed to interrupt him when a message needed action or came from family, with a draft reply ready. All afternoon it alerted him three times, for a bank message, a family email he answered from its draft, and a ticket itinerary change he needed to act on.
He runs AI on his homelab. He can ask the AI to throw an event on his calendar and it appears, and the setup can also send events to his primary calendar by email.
Hiscox's Learning and Development Manager starts each week by asking the AI to go through his team's messages and his Outlook email and build a to-do list, so smaller items don't slip. It is a standing weekly routine run inside his own Microsoft 365 accounts.
He pays per token for small API jobs. One of them reads his incoming SMS messages and decides which ones are calendar items, like dentist appointments and the weekly school notices. The whole setup cost him $1.50 over six months.
He pointed the AI Fable at a newspaper archive and asked for a timeline of wildfire events in and around the Adirondacks. The result is an interactive timeline built from 12,000 pages of newspapers.
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.