A random mix from the whole library. Shuffle for a new set.
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.
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.
His agent sweeps his email and call transcripts looking for work he missed, then drafts the follow up messages and tickets for him. It catches commitments that slipped past him in busy weeks.
His morning agent reads his email and builds a prioritized to do list with time blocks for the day. It also checks the weather and warns him to leave earlier when rain would slow his trip, which has twice saved him from showing up soaked.
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).
Across the same two-week inbox-and-calendar test, the AI proactively flagged every one of the author's seven calendar double-bookings before the meetings occurred.
He is treasurer for a nonprofit food co-op. He gave the AI the co-op's financial statements, some notes on what he wanted to explain, and the logos, and 20 minutes later he had a ten slide deck and separate printouts for the annual meeting.
Ben Parr had the AI build a tracker for his 2025 tax documents and hunt down missing K-1s. The agent organized the paperwork and chased the missing forms.
His agent reads his email, including PDF attachments, finds the dates and appointments inside, and adds them to his calendar with a check for duplicates. With two kids at different schools sending home a stream of letters, he calls it a big time saver.
A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.