Six agent teams, one loop

Six agent teams. Five research agents running in parallel on every Discovery cycle. Three ways to run each team — once, on demand, or on a schedule that repeats until you stop it. And one number that's easy to miss: zero human clicks between a bug surviving two rounds of verification and a fix actually landing in the build.

That last one is the one worth explaining, and the cover image on this post is the example. Overgrowth Station is an idle-reclamation game where vines slowly swallow an abandoned transit hub and you spend currency clearing them back. Nobody on our team designed it — the research agents pulled the idea out of a cluster of Reddit threads about "cozy management games with no fail state," the builder had it running in about forty minutes of wall-clock time, and the verifiers caught that the world layer was completely silent while the UI beeped away on every click. Nobody filed a ticket for that. The platform queued a follow-up fix run on its own, a later pass added the missing ambient audio bed, and the rebuilt version passed the full verification chain this morning. That's the whole pitch for what this platform is, condensed into one screenshot: a loop, not a tool, where the output of one team is the input of the next and gaps get noticed without a human standing watch.

Before the fix loop, there's the idea loop

Most AI builders start at the text box — you bring the idea, they build it. Fine if you already know what to build, but "what should I build" is a research problem before it's a product problem, and it's answerable with legwork: what people complain about in r/smallbusiness, what gets asked eleven times a week on a niche subreddit, what's sitting in an underserved App Store category's "you might also like" slot. The Discovery team does that legwork on a schedule. Five agents run in parallel — trend data, social discussion threads, Q&A sites like Quora and Stack Exchange, app-store category gaps, and a fifth that synthesizes: it reads what the other four found and looks for the same complaint surfacing in more than one place, which is usually what separates a real opportunity from a one-off gripe.

They converge on Opportunity Briefs, and a brief isn't a vibe — it names the problem in the words people actually used, estimates audience size, cites the evidence (thread links, quote snippets, search volume where it exists), and scopes an MVP. Not "a fitness app," but "a rep-counter for a specific under-40-second exercise category nobody's built a clean timer for." Click Build-this and that exact scope becomes the builder's prompt, no lossy translation in between. You can skip all of it and type your own idea, and most people do, at least at first — Discovery earns its keep more on your second or third product, once you've run out of your own ideas.

What actually caught the silent audio

The Builder team plans before it touches code. You get a short written plan, and it'll ask what it can't guess — per-device or account-linked saves, paid tier from day one or free-only for now. Skipping that question is how you end up with a builder that guesses wrong on something expensive to unwind later. Once you confirm, it builds while you watch a live preview update. The surface is wide — websites, web apps with real backends, 2D and 3D games, Android apps, desktop apps, browser extensions — and it's honest about pace: 3D games converge noticeably slower than a CRUD web app, and it says so up front instead of quietly taking three times as long.

The part that caught Overgrowth Station's missing audio isn't the builder at all. A separate set of verifier agents — not the same agent grading its own homework — reviews the code for correctness, audits it for security holes (injection, exposed secrets, routes missing auth checks), checks for broken links and basic SEO hygiene, runs accessibility tests against the rendered output, and confirms the build actually matches the plan. That last check exists because a builder can produce technically working code that quietly drops a feature the plan promised, when that feature turned out harder than expected. Findings go back for fixes, and the loop re-verifies rather than trusting the fix on faith. When something survives that anyway, the queued follow-up run picks it up later — hours, in Overgrowth Station's case — with no ticket, no reminder, no human noticing the gap first. More on how the chain itself is built in How builds verify themselves.

Shipping without handing you off to a reseller

A finished build goes live on a free subdomain in one click, deploys to your own server over SFTP, or ships to app stores through your own developer accounts — your Google Play account, your Apple account, your keys. We sit in front of none of it, which means you keep the account, the revenue, and the option to walk away without losing the app. The Ship team does the tedious packaging work: a real signed .aab through the actual Android toolchain rather than a wrapper, signed desktop installers, packaged browser-extension zips, store listings and privacy declarations written from what the code actually does rather than a generic template. An app that doesn't touch location data doesn't get a privacy form claiming it does.

Two things stay yours on purpose, not by limitation: the one-time developer registration fee, and the final rollout click that publishes to real users. We could automate around both with stored payment info and chose not to, for reasons the callout below covers. Full walkthrough, including what a rejected submission looks like, is in From prompt to app store.

The part most tools skip entirely

A shipped product with no feedback loop is just an expensive prototype, which is where most tools hand you a URL and disappear. Connect Search Console and Analytics and the Optimize team starts pulling real numbers daily — what queries you rank for and at what position, who clicks, what they do after landing. Store analytics (installs, retention, crash rates) feed the same dashboards for apps. It turns gaps into concrete proposals rather than vague advice: "this page ranks position 14 for a term with real volume, the title tag doesn't mention it, here's a rewrite." Pick your mode — it just reports, it proposes and waits for your approval, or it applies the change itself and watches for the metrics to move the wrong way, with a rollback path if they do.

The Marketing team drafts promotion that's native to wherever it's posted, and this took more iteration than expected. Early versions pasted the same three sentences into Reddit, X, and a Quora answer, and it read like exactly that. Now: a Reddit post tuned to that subreddit's tone with a planned first-comment reply, because on Reddit the real information often lives in the comment and the post is just the hook; an X thread that assumes a reader who bails after one bad line; a Quora answer that teaches something useful for two paragraphs before it mentions the product exists. The Ads team plans campaigns and drafts the creative — headlines, images, targeting — for platforms like Google Ads. Every draft from both teams sits and waits for you.

Where the loop stops on its own

Autonomous mode chains all six so research feeds builds, builds feed shipping, shipping feeds optimization, and the cycle repeats on its own schedule with no human re-triggering each stage. We run our own loop this way, and most of what's in our Showcase and Unity Lab came out of it unattended — nobody sat down and decided an idle-reclamation game should exist before Overgrowth Station did.