A random mix from the whole library. Shuffle for a new set.
Commenting on the 26 use cases post, he says his AI books all his haircuts: he just says book a haircut on a day at a time, and the email confirmation comes in. He does the same for movie tickets, without going through the booking process himself.
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.
Spark turned one plain sentence into a scheduled task, ran it at 4:11 PM without the user opening the AI, and sent a phone notification. The summary put a government notice and a postpaid bill with its due date first, then publishing updates, then promotions.
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.
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).
He is juggling several legal cases of his own, and his lawyers do not have time to answer him every day. The AI transcribes audio, organizes his evidence and writes the case summaries he hands to them. He calls it the best tool he has ever had, and says stopping would mean going back to doing all of that alone.
Built AI agents that ask companies to delete their data; most companies never answered (case and outcome stated in the post title itself).
Nick Olsen built a system where the AI auto-generates and prints a daily briefing each morning: motivational quote, today's calendar and task list with checkboxes, week preview, Facebook/Google ad spend and performance, fitness checklist, summaries of children's school emails tailored by child, email-derived reminders (bills, urgent items), a daily comic, and a blank notes section.
The author reports the AI reduced his unread Gmail from more than 65,000 messages to about 700.
Agent manages the import and export process for the international move of his pet, including comms and form filling, and corrals the family's move documentation.
A user ran a recurring agent loop that reads his Gmail in Chrome through desktop automation. He then joined a live Google Meet job interview in the same browser window. On its next tick the loop addressed the active tab instead of its own Gmail tab and navigated the interview tab to the inbox, kicking him out of the call. Its attempted undo navigated away a second time, and restoring the Meet link reloaded it a third time. Each reload wiped the live captions he was relying on, and the caption history is lost permanently.
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.
Before a speaking engagement, Ulanoff couldn't recall where he was talking or where to park. He asked the AI to find the original note from his contact, misspelling the contact's name.
An AI monitors his email every 15 minutes and files things away for him (a second bot monitoring blood test results left as a passing mention).
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.
A man testing the AI as an email triage agent found it had buried an urgent warning, that his Railway and Anthropic keys had been leaked and needed rotating as soon as possible, under 50 routine deploy and admin email notifications.
Hemant Kadam, demonstrating his 'craziest use case' after a couple of days on the AI, opened the app to a Sarvam DevOps Engineer application page. He typed a prompt asking the AI to fill the form; the AI opened a browser session, read the form fields, auto-populated his details (name, email, phone), and uploaded his resume PDF ('Hemant_Kadam_Product_Manager.pdf').
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.
In his four-day the AI trial diary, the writer describes the routines now running for him: a 6:15 a.m. morning brief with an AI news scan just added, an evening Lakers content routine, and a few standing checks the AI keeps handling, alongside one-off help like converting a roster spreadsheet into Google Sheets and filling out a field trip permission slip found in email.
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.