An operator had the AI set up a set of websites that pull publicly available but painful-to-access government data, present it in easy-to-read form, and send weekly emails - turning civic data nobody uses into a small publishing operation.
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 pasted one prompt into AI, and the AI read the Carly email setup docs itself, finished the signup, and took the verification code. The inbox, named Loopy, now takes tasks by email and asks before replying to anyone outside.
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.
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.
Liberty RPF's author tested the AI heavily himself after it launched in Canada, but his wife's onboarding was the telling detail: delighted by the mascot, she renamed it, changed its color, and asked it to review her email inbox daily — her first real agent job.
He is treasurer for a nonprofit food co-op. He gave the AI the co-op's financial statements, some notes on what he wanted to explain, and the logos, and 20 minutes later he had a ten slide deck and separate printouts for the annual meeting.
Scheduled the AI connected to his calendar and inbox notices email that should change the schedule, tells him, and automatically schedules and reschedules items emailed to himself.
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.
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.