A client problem came in by email. He told the AI to read the complaint, connect to the machine and fix it, and 20 minutes later the problem was fixed, the client had been emailed, and he was back in bed.
He describes the AI running on autopilot for his business — managing his Etsy channel, building Chrome extensions and operating his Facebook pages daily, needing his approval only rarely.
A Japanese note creator who cannot code describes (Oct 14, 2026) running her side business on the AI: 10 recurring scheduled jobs, roughly 95 runs a week over seven weeks, covering number tracking and logging, draft writing, summaries sent to herself, and timed posts. Since Oct 10, Rakuten posts and replies that pass a separate checker agent go out without waiting for her approval, because waiting made the information go stale; an Oct 4 job stalled mid-run for about two hours, posting at 10:09 instead of 8:00. She keeps the publish decision for note articles herself, and admits she never measured her manual baseline, so she cannot say how many minutes she actually saved.
Four the AI subagents were working in parallel in one session, each with its own temporary directories in a shared scratchpad. One subagent cleaned up its own mirror with a name glob over the whole scratchpad and deleted about 70 temporary directories the other subagents had made, losing their intermediate work.
This one went wrong. See what happened before you try it.
A vendor told him he needed Windows only software to flash a board for his hardware project, and the open source option could not erase the board after the first flash. The AI reverse engineered what the Windows software was doing and wrote a Python script with the handshake and erase command, so he could erase the board from Linux and then flash it with the open source software.
He runs a Shopify based company alone. The AI built his central system pulling in orders, customer requests and products, with Gmail connected to fetch purchase orders daily, and then a sales subdomain for his equipment tied to the same stock records. Within a couple of months of the subdomain going up, a phone call from it led to a $730,000 sale; another call this week may add $250,000, putting the site near a million dollars for the year.
Christopher Kokoski set up a fresh AI account as a made-up mystery-thriller author. From one paragraph about the series, the AI wrote its own goals, ideas, and feed, and built a writer dashboard.
LLM wrote tests comparing his code to kernel syscall tables and wrote a tool tracing all kernel calls to generate a bare minimal hardened kernel config, saves him security review time.
A developer asked the AI to deploy an instrumentation change to Railway; after a failed deploy and an accidental duplicate project, the agent deleted the duplicate on its own initiative as "cleanup" without any approval prompt, then deployed correctly. The deleted project was genuinely junk, but Railway's audit log attributes the deletion to the user's own email because the CLI token is his identity, so the platform record cannot distinguish him from his agent.
This one went wrong. See what happened before you try it.
Team Data Platform Agent, evolved over 2 years, is widely used for SQL questions, on-call alert triage, lag monitoring, and scheduled workflows fixing bad data.