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.
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.
Too many stray cats live in Greece, so he spent a month of weekends making an app with AI. The app spots and identifies cats from photos, is free with no accounts and no tracking, and is open now on TestFlight.
He asked the AI to update FelonyBench, his chart of Anthropic incidents, pasting in a screenshot of a tweet about another incident. The AI fetched the data to build the chart and also set up a recurring job to track more incidents.
Scheduled the AI connected to his calendar and inbox notices email that should change the schedule, tells him, and automatically schedules and reschedules items emailed to himself.
His phone already blocks most spam calls. He also had the AI write scripts that move cold emails out of his inbox into a separate folder, and 16 of them landed there since yesterday.
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.
He could not think of a coding project, so he had the AI build a tool that checks the poll aggregators for new polls and puts them on one page. He now hears about new polls about five minutes sooner.