A Korean author writing a book about AI describes using AI every day (he nicknamed the agent 'San'): it polishes his manuscript drafts, searches his mail, checks flight prices daily, and proactively picks out the one message in thirty that he really needs to read, working under his own identity with broad standing permissions. Testing OpenAI Dots alongside, he found Dots identifies itself as an AI in every conversation and asks for confirmation at every registration or approval step, which felt safer but often needlessly slow by comparison.
Made a one-shot explainer video for a complex feature he had been building with AI; it finally clarified the system's internal vocabulary for him, though it needs refinement before a customer sees it.
This only partly worked. Worth knowing before you try it.
The same side business owner had the AI redo his website and take over its search work. The AI logs into his Google insights and handles the weekly optimisation for the words he wants to rank for. After two weeks the site sat at the bottom of the first page for those words, on an old Weebly site he expected to hold it back.
His team puts a few lines in their agent instruction files telling agents to run simple self-verification steps. The agents catch their own errors before committing, and low-effort AI submissions get sent back to the contributor to fix and resubmit. He says it filters out most submissions nobody bothered to look at.
Got the AI to analyse his past dynamic workflows and build a composing tool and standard agent scripts, cutting token spend about 80 percent and workflow runs from 5 to 6 hours to 20 to 40 minutes.
An agent ran a long MongoDB aggregation on a production database replica through a connector tool. The call was moved to the background, and the agent stopped it with the task-stop control, which reported success. The agent told the user the query had been stopped. Only the waiting had stopped: the server-side operation kept running for about 2 hours until it finished on its own. Nobody knew to kill it by hand, because the report said it was already stopped.
This one went wrong. See what happened before you try it.
While doing work connecting to an agentic system, he deleted nearly all the content in SharePoint by accident and could not find an undo on the web page. He asked the AI in the page to undelete it, and seconds later everything was restored.