A random mix from the whole library. Shuffle for a new set.
Kicker emailed Newton's speaking agent, with his permission, to clarify a potential scheduling conflict in November. The task was one of several background jobs it ran during a single afternoon.
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.
His claim was too small for a lawyer and the insurer had frozen it at $4,430, so he worked it himself with AI holding every letter in order. The agent surfaced six dated contradictions in the adjuster's own letters, including a legal basis for denial that changed three times, and reviewed each of his drafts as opposing counsel before anything was sent. After his letter quoting their own paper back at them, the offers climbed: $6,500, then $8,000, then $8,750, and the insurer accepted his split of the last gap the same morning, at $10,250.
The AI cleared an inbox of 100,000 emails during the user's workday, leaving a manageable mailbox behind.
Hemant Kadam, demonstrating his 'craziest use case' after a couple of days on the AI, opened the app to a Sarvam DevOps Engineer application page. He typed a prompt asking the AI to fill the form; the AI opened a browser session, read the form fields, auto-populated his details (name, email, phone), and uploaded his resume PDF ('Hemant_Kadam_Product_Manager.pdf').
This summer he put the URL of FIFA's World Cup schedule into AI. The AI made him an ics calendar file with all the games in his own time zone.
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.
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.
Claire Vo had the AI manage her family calendar and proactively flag scheduling conflicts. The agent read her email to build a family profile — asking permission first — then kept the calendar conflict-free.
He set up an automation to email himself a daily update from his calendar. Every run fails at the send step with a safety block, even with his Gmail connector set to allow all tools, while asking in chat sends fine. He rebuilt it several ways and every version stops at the same point.
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.