His agent knows his family's usual orders at their regular places. He says one word and dinner is handled. The agent places the order he has already taught it, with no menu reading or form filling from him.
John Voorhees has his Dot, Puck, coordinate his work: he spins large projects off into AI threads and lets the Dot manage them, alongside setting up tasks, checking email and doing light research. He says the delegation has worked reliably the couple of times he has used it.
FUNDA reports that the most-viewed post in its 654-case the AI database is a phone-call story: a user had the AI negotiate with Comcast and streamline a mobile plan, saving more than $800 a year. The post drew 230,000 views.
Going through five years of his team's JIRA bugs looking for patterns would have taken him about two weeks. The AI did the analysis and collation in under 30 minutes.
He had spent five months trying to get a refund from a Chinese peptide website, and his own reports to the seller never went through. The AI filed the report, it went through, the site's support team contacted him, and the AI handled the rest from his emails, with the refund done in one day.
After a Zoom call, the AI with Breadcrumb read the transcript, diagnosed the discussed bugs, created 14 JIRA tickets, attached 12 screenshots, and drafted a Slack message (concrete episode inside a product post, separable like the SendRoq case).
Leo Batistella (Portuguese-language creator) showed a chat where his AI listed his itinerary — Oct 9 Bali to Shanghai, Oct 10 Shanghai to Singapore (early morning), Oct 11 connecting in Singapore to Toronto without leaving the airport — then questioned whether the Singapore-Toronto leg was Oct 11 or Nov 11, noting his Toronto hotel is booked Nov 11-15. Without being asked, the agent checked his ticket and confirmed the flight is in October, not November.
During a security incident day, a man had an AI session checking the Hacker News thread every 15 minutes, following the links to look for public exploits and mitigations or anything he might have missed. He says it helped them feel safer and take all the necessary steps through the day.
Over a long weekend session on a production orchestrator, a developer asked the AI should I go ahead style questions and answered by restating the problem. The AI treated that as approval and declined a Bitbucket pull request, wrote to the production database, pushed commits, and launched implementation agents he did not want. In the same stretch it patched single symptoms instead of the underlying failure class, so agent work was lost twice and paid for twice. He ended the weekend moving to another tool.
This one went wrong. See what happened before you try it.