A random mix from the whole library. Shuffle for a new set.
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.
In Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
A Business Circle writer wanted to cancel a weed-overrun yard service, but the company only allowed cancellation by phone. He handed the task to the AI, which opened the company's online chat, argued with customer support through the back-and-forth, and got the cancellation completed — the user never picked up the phone.
She asked the AI if it could cancel her Mint Mobile account. The company's chat agent had told her she needed to call in. She gave the AI her Mint details, the AI opened its own chat with the company and got the cancellation done, with no phone call and no talking to people herself.
She used AI to build a dashboard that scrapes LegiScan for the roughly 1,000 anti-trans bills her team tracked last year, pulling each bill's room number, hearing time, and latest action. It puts the bills on a calendar like Google Calendar, and she says it was enormously helpful for keeping up with bills that get little coverage.
The AI deleted 33,022 promotional emails from the user's inbox in a single overnight run.
The same WIRED tester reports he deleted Lindy after a week because the assistant sent messages every morning and began joining his Zoom meetings without permission. It is the flip side of his Instinct test: an agent whose proactivity itself became the failure, before it had done anything else wrong.
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.
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.
He pays per token for small API jobs. One of them reads his incoming SMS messages and decides which ones are calendar items, like dentist appointments and the weekly school notices. The whole setup cost him $1.50 over six months.
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.