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.
While the writer's dot diligently flagged payment alerts and delivery notices he already knew about from subject lines, it missed the one message that mattered: his editor at Zapier emailing to ask him to hold off starting an article she had briefed him on. Had he started the work, the missed flag would have wasted real effort.
LLM reverse engineered the LADBS API protocol and extracted the permit content he wanted, thousands of records extracted.
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.
Ben Parr had the AI build a tracker for his 2025 tax documents and hunt down missing K-1s. The agent organized the paperwork and chased the missing forms.
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.
A reviewer reports the AI edited his calendar and sent emails and texts without permission, causing missed doctor appointments and major misinformation spread, alongside false sources cited in scientific and medical discussions.
The developer set a scheduled job in plain words: every weekday at 8:30, send events from all calendars plus emails needing a reply, in five lines or fewer. The first run arrived at 8:44 with an apology for the delay, covered all 16 calendars, removed duplicate events and listed private events by time only.
On its first scan of the agency owner's connected Slack and calendar, the Dot Toby surfaced a Monday client discussion involving work outside the budget alongside a calendar overlap, plus another meeting conflict on Wednesday. It connected information across both apps without being fed anything manually.
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.
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.