A random mix from the whole library. Shuffle for a new set.
He needed to know if a library near him had outlets. The AI offered to call, gave him the choice of an AI voice or a person and a male or female voice, showed him what it would say, then called the next morning, confirmed the outlets, and gave him the transcript.
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.
He uploads his own data and points the AI to specific sources and documents, with examples he made before to show the format he wants. The AI then builds the tables and graphics for his Education Rights Project, public pages on education rights and funding in US states, with policy briefs, slide decks and interactive widgets.
Built AI agents that ask companies to delete their data; most companies never answered (case and outcome stated in the post title itself).
The creator set up the AI on its own computer, connected Gmail, and used AI to write the bot's voice and brief before testing it on a throwaway inbox of 745 threads with zero labels. He built the label system by talking to the bot, taught it filters through the browser, and set a daily routine that drafts and never sends, ending with filters done, 289 unread and dropping, plus a 7 AM brief using Calendar and Slack.
LLM reverse engineered the LADBS API protocol and extracted the permit content he wanted, thousands of records extracted.
During a 30-day trial diary, the author shows the AI filling out a school field-trip permission slip it had found in his email — one of several family-admin tasks it handled from his accounts.
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.
The AI was fed government forms, UI design and legal requirements and produced the app in 1 hour; the team completed conversion of 150+ forms in 2 weeks with one person versus a year before.
A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.
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.