Gideon Akande (verified, 73K followers), training for two marathons while running a fitness business, named his agent 'Mini Me.' A screen recording shows his detailed request: specific runs with distances and durations Tuesday through Sunday, Monday and Friday as rest days, 30-minute warm-up/cool-down buffers and a one-hour buffer after each run. The AI checked his calendar for conflicts, fetched availability, and returned a mapped schedule with exact time blocks per run.
He connects an AI to his posting app with one key. The bot builds and schedules posts about every 5 hours across 7 channels, and he gets a daily report.
A third anecdote in Simmons's roundup describes a Dot that kept emailing a hotel for two days, then found the general manager's name and emailed them directly. The eventual outcome of the escalation is not stated.
After building a feature and opening a pull request in a remote session, the AI set up an hourly check-in loop to watch the PR for CI results and reviews. Nobody asked for monitoring. Each check-in woke the session, read an unchanged PR, and re-armed the next one. The loop ran about 3.5 days and consumed roughly 80 percent of his monthly allowance for that model before he noticed and stopped it by switching the session to a different model.
This one went wrong. See what happened before you try it.
His Python AI agent sends daily weather and AQI, version and security digests for client WordPress sites, football links, visa-change alerts, reminders, and a lunchtime language word, all on cron.
A man at a company that paid $300,000 a year for Looker for ten years says one engineer, working part time for a couple of months with AI, built a home grown replacement for their dashboards. The core idea checked out in a couple of weeks, and the company told Looker it will not renew.
He set up an auto-sync of his Goodreads updates to BookHive with help from the AI and val.town, so both places now hold the same content, including his new review of Slaughterhouse-Five.
Built with agents over about a year: a production billing system for his small telecom company, a multiplatform app, internal tools in use, and a coding agent harness now used by non-technical colleagues.
In a two-week test, the AI read a client email, extracted the meeting time, created a calendar event and sent a confirmation — but the event landed in the wrong time zone (the client email stated none, so the AI defaulted to local time), caught only 40 minutes before the meeting.
This only partly worked. Worth knowing before you try it.