The AI told him swap memory on his server was high, found the cause, and had the fix ready for him to approve. The AI or the AI now connects to the box, upgrades services, and sorts out problems, so his site and newsletter run on a bare DigitalOcean droplet instead of a pricier platform that makes hosting easy.
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.
This one went wrong. See what happened before you try it.
An old printer orphaned by macOS 27 got a second life: The AI wrote the driver while using its owner as the diagnostic instrument - asking him to judge whether each line was progressively less visible, whether page one's DPI was lower - until the printer printed correctly again.
A developer built himself an AI evening edition. It goes through the posts and articles he saved, checks each one against his actual setup, and sorts them into adopt, trial, park or skip. Any change it suggests waits for his yes. The first run cleared his whole backlog of 30 items, and a planted fake post with hidden instructions was flagged and skipped.
Graham McDermott posts that he started using AI to understand his Verizon upgrade options, and it identified a bookkeeping error on his wireless account and had him change the autopay account routing. The fix saves him $24 per month with minimal effort.
He told the AI to request anything it could get sent to him for free, with no limits set. So far a fabric sample and a lot of state travel guides have arrived, and he is a bit worried about how much more is coming.
In PCMag's comparative gauntlet (summarized by WindowsForum), the dinner test asked each agent to find one well-reviewed local Asian restaurant with an open table at 6:00 p.m. that evening. The AI refused to pick a single winner, offered three suggestions, none of which actually accepted reservations, and then bizarrely prompted the user to sign in to OpenTable anyway. Dots found a 6:15 p.m. slot and flagged it as the closest to the request.
This one went wrong. See what happened before you try it.