A random mix from the whole library. Shuffle for a new set.
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.
Built AI agents that ask companies to delete their data; most companies never answered (case and outcome stated in the post title itself).
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).
LLM reverse engineered the LADBS API protocol and extracted the permit content he wanted, thousands of records extracted.
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.
TechMitra founder Ayush Singhal asked the AI to triage his Gmail thread by thread. It proposed archiving ten promotional emails, correctly found nothing to do on other categories, and unprompted flagged a spam comment on his second website. After his approval it archived nine FYI threads and left two genuine action items.
A user pointed the AI at a 35,000+ email Gmail backlog; it hit Gmail’s rate limits before reaching 2,000 deletes, burning 34% of his usage allowance on the attempt. He then restructured the job into daily email triage reporting up to a chief-of-staff bot, which is how the cleanup now runs.
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.
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.
A father's son grew his hair since Covid and cut it to donate to a charity that makes wigs for children with cancer. The father kept putting off making a poster, then gave the AI a couple of photos and a video link and it built the poster while he worked. His boss put it up, workmates pledged enough to fund the wig, 250 pounds. Later, from the car, he voice prompted the AI to remake the poster in his son's words for the boy's school, and forwarded it on WhatsApp when they arrived.
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.