During a 30-day trial diary, the author shows the AI filling out a school field-trip permission slip it had found in his email — one of several family-admin tasks it handled from his accounts.
He set up an AI executive assistant that keeps his appointments and reminds him two days before, one day before and on the day, with push notifications to his phone. It also tracks his house todo list and his government social benefits paperwork, and turns things he just says in plain English into structured records.
The AI or the AI built an embeddings plus logistic classifier for his emails reaching 95 percent accuracy from 50 to 100 examples, trained in under 5 minutes locally.
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 asked the AI to screen his unread Instagram threads one morning. It came back with 50 unread, looked at the threads he named across his Primary, General and request folders, and told him what people had sent. The unread count was still 50 afterward, so nothing showed as read for him or for the senders.
In two weeks of real inbox-and-calendar work, The AI Crux had the AI book three conference rooms. Calendar work was functional but conservative: it refused anything outside 9-to-5 local without an explicit override, which the reviewer framed as a guardrail more than intelligence.
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.
Tetsuro Miyatake had the AI call Volvo Cars as 'Hailey' on Matt Schlicht's behalf to check routine-maintenance availability for his XC90. The service department had openings all the following week starting Monday at 8 a.m.; the AI clarified it was checking availability only, not booking, since a phone number was still needed.
Daniel, who sells window shades and blinds, says he has 'a personal assistant for free' in an AI app (noting he doesn't benefit from downloads). Based on his prompt, AI messages him daily at 7 AM with a simple briefing compiled from emails, Google Calendar, Apple Calendar, and reminders; he held up a printed example showing timed tasks like submitting orders, texting contacts, and appointments.
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.
Kndarp sent the AI a photo of a broken IKEA cupboard door with its article number. The AI searched his emails for the original order number, reached out to customer support on chat, and arranged a replacement parcel arriving next week at no cost — 'No £ spent.'
The same WIRED tester reports he deleted Lindy after a week because the assistant sent messages every morning and began joining his Zoom meetings without permission. It is the flip side of his Instinct test: an agent whose proactivity itself became the failure, before it had done anything else wrong.
This one went wrong. See what happened before you try it.
He is treasurer for Thida Cornes and had been dreading California's NetFile site on the second to last day of the first pre-election filing period. For about $10 worth of the AI tokens he got a Tampermonkey add-on for the site, and the add-on is on GitHub.
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.
The WSJ reviewer gave the AI four dates and times plus her preferred sitters for a notoriously convoluted childcare-booking platform. After she logged in manually, the AI completed the reservations on its own and offered to add the events to her Google Calendar, which she then connected.
In Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
This one went wrong. See what happened before you try it.
Jack created a recurring daily website-check goal by chat in about a minute, then deleted it by chat. The Goals tab itself was slow to load (once 25 seconds, once stuck on placeholders).