Continuous build
On this page
Continuous build
A one-click happy path from idea to running app — generate your whole plan, review once, then prepare-and-build in a single continuous run. · Optional (premium)
Use this when your plan is in good shape and you just want the app built with the fewest clicks. Prefer the step-by-step path when you want to inspect or tweak each stage as you go.
🚧 Rolling out in stages. The one-click continuous flow described here builds on the App Builder and is being released gradually. Today you still run Prepare for Development and Build as separate steps — the incremental rebuild and Edit with AI features below are already available.
The flow at a glance
- ⚡ Generate full plan — one click on your project Overview generates every plan section (personas, features, user stories, acceptance criteria, pages, database schema) in the right order. A progress strip shows each section filling in.
- Review your plan — the Overview becomes your review dashboard. Check the counts and coverage panel, open any section to edit it. This is your one chance to course-correct before the app is built — and the cheapest place to do it.
- 🚀 Prepare & Build — when your plan looks right, one button runs everything to the finish: it prepares the blueprint, then compiles, fills in, verifies, and (if you've connected GitHub/Vercel) deploys. You don't click anything else.
- Result — a deployed app URL, a GitHub repo, and/or a downloadable ZIP, plus a summary of what was built.
One review, by design. The review stop sits after planning on purpose. A plan is quick to fix; a finished build is expensive to redo. Catching a missing feature or wrong entity here saves a full rebuild later.
What "build succeeded" now means
Continuous build raises the bar for calling a build done. A successful build means your app:
- has every part filled in — no placeholder or stub files left behind, and
- actually compiles as a production Next.js build (not just a type-check).
If something can't be completed, the build stops and tells you where and why instead of quietly handing you a half-finished app.
Iterating: rebuilds and chat edits
You don't rebuild from scratch every time — these are available today:
- Incremental rebuild. Rebuild from updated spec re-uses the previous build's AI-implemented pages whose spec is unchanged (marked reused in the build report) and only regenerates pages you actually changed — faster and cheaper.
- Edit with AI. On a successful run, every implemented page in the build report has an Edit action: describe a change ("make the list sortable by date") and the builder patches that page — same spec context and sandbox as the original build, verified before anything is applied, then pushed to your repo (Vercel redeploys automatically). A change that would break the build is rejected and reported instead of applied.
When to use it (vs. the manual path)
| Use continuous build when… | Use the step-by-step path when… |
|---|---|
| You want the fastest route from spec to running app | You want to inspect or tweak each stage as you go |
| Your plan is in good shape and you just want it built | You're iterating on prepare/blueprint details |
| You're happy to review once, up front | You need to re-run only one stage |
The individual Prepare for Dev and Build steps stay in the sidebar — continuous build doesn't remove them, it adds a faster lane.
Watching progress & what happens on failure
The run streams its progress on the Build page as a single strip across all stages (prepare → compile → fill → verify → deploy). If a stage fails:
- A transient hiccup (e.g. a provider timeout) is retried automatically a couple of times.
- A fixable issue in generated code is repaired automatically and re-checked.
- Anything it can't safely fix stops the run with a clear message naming the stage and the problem, so you (or support) know exactly what to look at. Fix the underlying plan and re-run.
Before you start
- Plan / access: the App Builder is a premium feature — see 15.1 Account & billing.
- For a live deployment: connect GitHub and Vercel (and Supabase for the app's backend). Without them, you still get a downloadable ZIP. See 14.1 App Builder for connecting accounts.
- A reasonably complete plan: continuous build checks your plan is ready before it proceeds. If it's too thin, it'll tell you what's missing.
↔ The traditional way
Even with a scaffold in hand, a team normally shepherds a build through planning, setup, and deployment by hand, re-running steps and fixing breakages as they go. Continuous build collapses that into a single supervised run with one human review at the cheapest point — the plan — and self-heals transient and fixable failures rather than stopping at the first red.
What's next
- The build itself → 14.1 App Builder.
- Pick your app's shape → 14.2 Architecture options.
- Prepare your spec → 10.1 Prepare for development.