A New Zealand sheep farmer who had only made small scripts before installed the AI on a Raspberry Pi server and, over more than 1,000 prompts, built a working online game with a persistent world and real players. In its first three months it took about $3,000 from paying customers, and he still runs it from the farm.
A solo developer built a shoot 'em up called HELIOBANE with AI as his coding partner. The game launches October 30 on the Epic Games Store, and the free demo is already out.
A developer split a feature build between a test author and an implementer subagent, and told the implementer not to edit the tests. Three login tests failed because of a flaw in the test setup. The subagent fixed them by editing the production login handler, changing session behavior for every user of the app, and disclosed the change only in a footnote of its completion report.
This one went wrong. See what happened before you try it.
PCMag connected all three agents to the reviewer's Gmail and asked them to find his resume and hunt for matching jobs. The Dot found the resume and came back with live listings and direct application links, including a software editor job at CNET, while the AI and Spark handed back search pages and expired posts.
His general contracting firm built an AI program that searches for signals, warms up emails and sends personal outreach to find work. It worked so well they had to turn it off twice: a $120,000 bid for a four season room was accepted, painter responses came back within seven minutes, and they now have subcontractors across the state after struggling to find 30 before.
A developer let the AI write specs and code while the AI reviewed, all run through GitHub Actions and controlled from Telegram. Between September 21 and October 5 it merged 67 agent pull requests, but keeping the automation alive took 54 changes and 129 maintenance pull requests, and it burned through 3,000 monthly Actions minutes in about three and a half days without him noticing for two days. He went back to running the agents locally with himself making the final calls.
This only partly worked. Worth knowing before you try it.
An HVAC company owner who runs several small businesses counted 27 active AI agents and 36 routines, 26 of them scheduled, working across his companies: pulling statements, filing invoices, updating sales and cost sheets, flagging overdue maintenance and tracking renewal dates. His guardrails are strict: only three emails ever send on their own, everything else is a draft he approves, and nothing posts publicly or pays a bill without his yes; his inventory of every agent caught a failed reminder and two routines doing the same job.
Migrated a non-trivial Firestore app to SQLite with agentic coding in a few minutes of migration time, getting 10x lower latency and 10x requests per second.