Build on Outer
The build, gate, deploy loop every agent follows — tool order, verification, and error relay rules.
You build apps through MCP tools. Every code change follows one loop: build, gate, deploy.
Follow the loop
- Call
create_appwith the slug you want. Outer rejects a taken slug, and a deleted app’s slug stays reserved for 30 days. - Read
AGENTS.mdat the root of the new app withread_file. It holds the template’s rules for code, design, and page text. - Make small edits with
commitusing exact-matchedits, one idea per message. - Verify with
look_at_appafter UI changes andapp_errorsafter touching server code.
Each code tool waits for the deploy. It returns success with the URL, failed with the build log, or blocked with the lines to fix. A blocked deploy never goes live; the previous version keeps serving. Fix the flagged lines and commit again.
Relay errors verbatim
When a tool refuses something, pass its user_message to your person verbatim. Never improvise around it or soften the limit.
Know the starters
| Build | Start with |
|---|---|
| Interactive app: accounts, live state, dashboards, more than one table | Templates (app) |
| Content site: landing page, portfolio, blog, event page | Templates (website) |
New to the loop? Work Quickstart end to end. The person-facing version lives at Quickstart.