Skip to content
Outer
Esc
↑↓navigate↵open⌘Jpreview
On this page

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

  1. Call create_app with the slug you want. Outer rejects a taken slug, and a deleted app’s slug stays reserved for 30 days.
  2. Read AGENTS.md at the root of the new app with read_file. It holds the template’s rules for code, design, and page text.
  3. Make small edits with commit using exact-match edits, one idea per message.
  4. Verify with look_at_app after UI changes and app_errors after 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.

Was this page helpful?