A random mix from the whole library. Shuffle for a new set.
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.
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.
Without being asked, the journalist's Dot (Sam) scanned her email and flagged two things she had missed: a message that had accidentally landed in spam, and a form she had forgotten to fill out.
A non-developer used AI to restore his foundation's broken donation payments and restructure the portal into four separate funds; the site shows $17,149,000 in donations processed.
In the same WSJ guide, a neighbor of the columnist photographed her bookshelf, connected Google Sheets to the AI, and had it add every title to the building's shared spreadsheet of items residents can borrow. The columnist then did the same with her own shelf.
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.
The AI sent a notification that it had spotted an email from TripIt, the vacation-planning app Ulanoff uses, about a password change he had forgotten making. The agent wanted to make sure he'd seen the email verifying it was him.
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.
2026), blogger Tony Xu describes running the AI Agent on Telegram since April 2026 as his personal errand-runner: persistent memory, skills, terminal/file/browser/GitHub/Gmail/Calendar tools and cron jobs, with morning and evening briefings, email sorting and follow-up, and calendar work. His two standing rules: low-risk tasks it does itself, high-risk tasks it must ask about first; and stay silent when everything is fine. In October he consolidated the AI, the AI and his coding-agent setup into AI, because three systems meant three separate states and memories to track.
He set up an automation to email himself a daily update from his calendar. Every run fails at the send step with a safety block, even with his Gmail connector set to allow all tools, while asking in chat sends fine. He rebuilt it several ways and every version stops at the same point.
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.