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.
Before a speaking engagement, Ulanoff couldn't recall where he was talking or where to park. He asked the AI to find the original note from his contact, misspelling the contact's name.
The road to a takeoff spot they fly from was not on OpenStreetMap, though satellite images showed the track. They built a tool called osmctl, and the AI drove it and mapped the road.
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.
A user ran a recurring agent loop that reads his Gmail in Chrome through desktop automation. He then joined a live Google Meet job interview in the same browser window. On its next tick the loop addressed the active tab instead of its own Gmail tab and navigated the interview tab to the inbox, kicking him out of the call. Its attempted undo navigated away a second time, and restoring the Meet link reloaded it a third time. Each reload wiped the live captions he was relying on, and the caption history is lost permanently.
This one went wrong. See what happened before you try it.
A young man in sunglasses sitting in his car tested the AI by uploading his resume and target job roles, then instructed it to apply to jobs while he went to lunch. Screen recordings showed multiple browser tasks running and a notification confirming an application submitted to 'ioTech Solutions.' The AI asked for information once for the first application, then reused it — resulting in 50 applications submitted while he was idle.
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.
Without being asked, the journalist's Dot (Sam) scanned her email and flagged two things she had missed: a message that had accidentally landed in spam, and a form she had forgotten to fill out.
The author describes using AI to resolve a six-month-old travel medical insurance claim with Cigna. The AI called the insurer, was transparent about being an AI, conducted the call politely (impressing the representative), and — because final consent was required — called the author's phone and connected the parties so he could approve verbally.
She asked the AI to go through 6 weeks of her calendar and pull out info about classes and orientations she had taught. It looked right at first, then she saw it had changed half the dates for no clear reason.
This one went wrong. See what happened before you try it.