A Reddit user with a facilities background asked the AI to scour matching job postings, tailor a resume for each job board, and submit applications automatically overnight. Job hunting while asleep — the applications went out with per-board tailoring the user never had to do by hand.
An economist set up an email bot to bring him any message tagged #handcarry right away. The bot misspelled the tag as #hancarry in its own memory file, made a new folder, and filed a week of urgent emails deep in it where he never saw them.
This one went wrong. See what happened before you try it.
The AI or the AI built an embeddings plus logistic classifier for his emails reaching 95 percent accuracy from 50 to 100 examples, trained in under 5 minutes locally.
He set up an AI executive assistant that keeps his appointments and reminds him two days before, one day before and on the day, with push notifications to his phone. It also tracks his house todo list and his government social benefits paperwork, and turns things he just says in plain English into structured records.
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.
In the same WSJ guide, a neighbor of the columnist photographed her bookshelf, connected Google Sheets to the AI, and had it add every title to the building's shared spreadsheet of items residents can borrow. The columnist then did the same with her own shelf.
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.
This one went wrong. See what happened before you try it.
The AI sent a notification that it had spotted an email from TripIt, the vacation-planning app Ulanoff uses, about a password change he had forgotten making. The agent wanted to make sure he'd seen the email verifying it was him.
Without being asked, Harry McCracken's Dot began flagging incoming messages it judged urgent or important in an inbox flooded with PR pitches. It also resurfaced an email from a freelance author that he had overlooked for weeks and nudged him to respond.
A man was spending 90 minutes a day on email. An AI agent was set up to read, sort and draft replies to every routine message. He now approves the drafts in 8 minutes, saving 82 minutes a day.
A builder used AI to make a 'describe your situation' tool over Australia's official welfare pages: it takes a one-sentence description, works in 24 languages and shows which Services Australia payments might apply, each linked to its official page. Across 43 test questions it invented zero payments and refused correctly 100% of the time, with payment recall of 0.76.
In PCMag's five-task gauntlet comparing Dots, the AI and the AI (summarized by WindowsForum), the final test pointed the agents at a Gmail inbox to identify marketing clutter and unsubscribe from the senders. The AI identified the emails but failed to launch its browser to actually follow through on external unsubscribe links when required, leaving the execution undone; Dots, by contrast, catalogued 700+ senders and clicked through unsubscribe pages.
This one went wrong. See what happened before you try it.
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 pointed the AI Fable at a newspaper archive and asked for a timeline of wildfire events in and around the Adirondacks. The result is an interactive timeline built from 12,000 pages of newspapers.
After his motorcycle was stolen, his insurer offered nearly half the market value. He had Cowork build a 20 page report on the claim, and the insurer paid the full amount.
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.
This only partly worked. Worth knowing before you try it.
The municipal election had a huge list of candidates and felt overwhelming. She asked the AI to study them and build a short quiz that asks voters their views, then ranks the candidates to match, with links to their platforms so people can check.
His local school division released the raw answers to a touchy redistricting survey as one PDF of more than 3,000 pages, which nobody could realistically read. He used AI to write scripts that pulled the answers out and built a public web page where people can search the responses and filter them by keyword and by school.