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 AI updated a website he manages for a charity and on its own scanned beneficiary header images to add information to the writeup; done well.
The same Cowork setup checks his father's email for work orders and schedules his father's meetings automatically. He turned off data sharing with AI for this, so the mail is not saved anywhere else.
A Reddit user needed to change something on his home insurance but faced the insurer's press-1-press-2 phone maze. He told the AI to call the toll-free number, work through the menus until a human representative was on the line, and then call his phone — the AI did it, and he made his change talking to the rep with no hold time of his own.
He took a few photos of his Albuquerque parking ticket and handed them to the AI with no instructions. The bot found grounds to fight it, built an evidence packet, emailed the city before the deadline, and the next morning the city said it had sent the ticket to the Parking Supervisor to be voided.
Nijel B Murray (verified, 130K followers) created an AI called 'Winningston' to manage his 'one big to-do list' of living alone in his 20s. Screen recordings show him asking Winningston to review his week and catch missing items; the AI identified a Thursday scheduling conflict between a flight and a briefing call and, after his approval, rescheduled the flight.
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.
Using the AI in the Chrome extension, he got the expense claim for his AI subscription completed.
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.
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.
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.