A random mix from the whole library. Shuffle for a new set.
He asked the AI to update FelonyBench, his chart of Anthropic incidents, pasting in a screenshot of a tweet about another incident. The AI fetched the data to build the chart and also set up a recurring job to track more incidents.
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.
He had the AI collect his will and trust documents and check them against state statutes. The review found missing signatures, an illegal clause, and outdated law references, and he fired his attorney the same day.
He follows the CNN lawsuit over White House press briefing access. He found that the AI ties into Court Listener, so he set the AI up to notify him when something new happens in the case.
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.
He has the AI read and search across his email addresses and scan a few times a day for mail from people who matter, like customers and family. He has basically stopped checking email forty times a day. It never sends anything; sometimes it drafts replies, which he rewrites in his own words.
Tetsuro Miyatake had the AI call Volvo Cars as 'Hailey' on Matt Schlicht's behalf to check routine-maintenance availability for his XC90. The service department had openings all the following week starting Monday at 8 a.m.; the AI clarified it was checking availability only, not booking, since a phone number was still needed.
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.
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 pays per token for small API jobs. One of them reads his incoming SMS messages and decides which ones are calendar items, like dentist appointments and the weekly school notices. The whole setup cost him $1.50 over six months.
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.