He ran AI on the task with 6 agents at a time, about 75 agents in total over about 6 days. They produced transcriptions of tens of millions of handwritten images and indexed them all.
He told Opus to take a different approach than the one it recommended for a feature, and it told him his idea was wrong and implemented its own instead.
This one went wrong. See what happened before you try it.
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.
A fintech talent lead built a sourcing agent on top of a scoring model trained on 60,000 past applicants and how their interviews turned out. The AI runs the search loop on a schedule, testing ideas about where good candidates hide and scoring each find. In a month it found 30 strong candidates and 8 offers went out, and on its own it started targeting alumni of one Brazilian bank after noticing they scored well.
He asked the AI to check a document against his checklist. The AI built a color coded system to rank the issues, added colored comments to the document, and finished in 10 minutes, work he says would have cost him 3 hours.
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 teacher asked the AI to make a presentation from her pacing calendar. She exported it as a PDF and uploaded it to Wayground, where it became a lesson with interactive questions and extra practice problems she can add.
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.
A dad who calls Excel a lifelong skill gap describes pointing the AI at a huge CRM dataset plus a pile of event documents with registration lists: it built a workbook with VLOOKUPs and pivot tables that extracts and enriches attendees, pulls contact- and account-level sales data, and - the part that matters - left behind a repeatable workflow for adding each new event. Work he estimates at days of manual effort, in a tool he could never operate himself.