A random mix from the whole library. Shuffle for a new set.
Volunteered and built a cartography data pipeline with coding agents for an educator, integrating sources updated every few minutes so new maps appear within about 5 minutes on a low-powered machine.
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 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.
His morning agent reads his email and builds a prioritized to do list with time blocks for the day. It also checks the weather and warns him to leave earlier when rain would slow his trip, which has twice saved him from showing up soaked.
Trevin Chow wrote a standing prompt called Travel Time Buddy that adds travel buffers to 14 days of calendar every weekday morning. The agent keeps his schedule padded against transit time.
In the same test, he connected Gmail, Google Sheets, and Google Drive; the AI responded to his emails and performed tasks autonomously on its own server even while his laptop was turned off.
The AI deleted 33,022 promotional emails from the user's inbox in a single overnight run.
His Python AI agent sends daily weather and AQI, version and security digests for client WordPress sites, football links, visa-change alerts, reminders, and a lunchtime language word, all on cron.
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.
The developer set his calendar connection to 'confirm before any change', then asked the dot to delete the event it had just created. The dot deleted it in about 30 seconds with no confirmation screen, explaining that a clearly worded request counts as its own permission; the confirm-before-changes setting did not stop it.
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.