Several parallel AI agent sessions (Opus 5.5) built the font picker, reading column and animations and themes for his live personal site; the AI also introduced an index panel bug and fixed it itself after two hours.
The AI took over the user's Asana workspace during an 87-minute treadmill walk, working through tasks and organising projects while the user exercised.
Claire Vo ran AI for several weeks and shut down every the AI she had. Her nine bots include Chief, which sweeps six inboxes and several Slack workspaces, a family bot that prints a kitchen table newspaper for her kids each morning, a helpdesk bot getting five star reviews, and a bot that audits subscriptions and negotiates insurance.
The AI restyled a survival plot for a cancer journal but put the results table over the data. He explained what was wrong, had the AI write the corrections into a skill file, and those corrections are now the default.
This only partly worked. Worth knowing before you try it.
Creator Amie Tollefsrud gave the AI access to her Instagram analytics and asked for growth advice; after three clarifying questions about audience and positioning, the AI delivered an 'Instagram Growth Plan' PDF. Screen recordings show an executive diagnosis (1.85M accounts reached), audience positioning, four content pillars, keyword clusters, carousel and story blueprints, and a 7-day action checklist.
Prompted an agent to build a custom LLM coding harness with session resume, done in an hour and working nearly flawlessly, plus a WebFetch tool added in 5 minutes.
His company runs three coordinated agents on its product account: one watches mentions and a watchlist, one writes posts and replies, and one controls quality. Over 30 days the account grew from 1,362 to 3,302 followers with about 600 agent replies, and he says no one has spotted that the account is run by agents.
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.