A solo founder runs his game key store with about a dozen AI sessions, one each for code, pricing, copy, bookkeeping and suppliers. They stay in sync through a shared record where facts are only ever added, each fact says whether a session confirmed it or just read it somewhere, and his decisions go into a numbered ledger the sessions look up instead of asking him again.
He spent 4 weeks designing and testing an upgrade of their 16 node HPC cluster with AI, and the AI then did the full reinstall itself. The reinstall covered remote install, network booted images, Slurm setup, a shared filesystem, and web services that give their users a small cloud platform.
Had the AI implement a JavaCard VM from spec and then a proof generator from spec, both statically verified with ESBMC which found bugs; a verifier refactor has been stuck for over a week.
This only partly worked. Worth knowing before you try it.
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.
An engineer at Sumasate writes that his team connected the AI Tag to GitHub, Sentry, their database, log tools and Notion, and let it do the first look at every alert in Slack. After three months, fixes finished inside alert handling went from about 2 of 38 alerts a month (5.3 percent) to about 7 of 44 (15.9 percent).
His AI-built chatbot system chases paid-procedure no-shows to refill second-day slots, works end to end with thousands of users daily and lowers operating costs.
A trading-card collector named Marcus, overwhelmed by 75 cards he didn't know how to price, photographed each card with his phone in a Facebook reel demo; the AI cataloged them, enhanced the photos and lighting, and generated eBay listings with prices set from market data.