A random mix from the whole library. Shuffle for a new set.
UFC fighter Justin Gaethje (verified, 3.7M followers) introduced his AI 'Highlight' for his training, travel, and business schedule. A notification reminded him of a Phoenix flight; he asked for tee times and the app showed options (Legacy, Aquila, Raven, Encanto) — he booked Raven Golf Club at 1:30 PM.
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.
This summer he put the URL of FIFA's World Cup schedule into AI. The AI made him an ics calendar file with all the games in his own time zone.
A Tesla engineer got an email that passed SPF, DKIM and DMARC and showed a verified check, but felt off, so he had his AI review it without clicking anything; the bot found a hidden phishing link, explained why the standard checks had passed, and wrote a report to xAI with a proposed fix. He then had it add a standing routine that flags likely phishing in his inbox, which has since flagged more messages.
Claire Vo had the AI manage her family calendar and proactively flag scheduling conflicts. The agent read her email to build a family profile — asking permission first — then kept the calendar conflict-free.
Around Elmira and Corning, New York, event listings were scattered across library systems, a brewery site, a school app, chamber newsletters and Facebook, so people found out about things the day after. He had the AI build one page that checks 101 sources across three New York counties and part of northern Pennsylvania: 1,855 listings over the next 90 days, 1,767 events after duplicates are merged, about 250 in any week, at 159 venues. A cron job reruns it every six hours on cheap shared hosting, about 8,300 lines of PHP, and cancellations mostly handle themselves because an event disappears when its source stops listing it.
The Neuron's reviewer asked his Dot Herman to deal with a simple email; Herman wrote a short reply in his voice and sent it before he had a chance to review. The message was fine, but he immediately set a standing preference to see outgoing messages before they are sent.
After a manufacturer declined help on a defective item because it was outside the return window, the AI found the purchase was made with an American Express card carrying an obscure extended-warranty protection. It submitted the claim on the author's behalf and obtained the refund.
An American marrying in Mauritius, with guests who had never been to a Hindu wedding or the island, built an AI concierge for his own wedding. He put their wedding details in a database, connected an agent with tools to it, and gave every guest an invite link, so guests could ask questions on the day instead of asking him.
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.
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.