A random mix from the whole library. Shuffle for a new set.
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.
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.
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 had the AI work out how the When2Meet scheduling site works and turn it into a skill. Now the AI can read his calendar and fill in the When2Meet availability grid by itself.
Ahead of an apartment move, a reviewer asked the AI for a day-by-day packing schedule. The AI built one with sessions capped at 30 minutes, sequencing items so things the person won't need before the move get packed first.
Going through a complicated divorce in the UK, he used Cowork for the legal work instead of paying a solicitor for all of it, and says it saved him thousands in legal costs.
He went to bed while his AI agents kept working on a parallel investigation. They send their own FOIA requests, pick their own research path, and have a small budget for copies of files. He set the web permissions for the night before letting them loose.
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.
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.
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.