Landing pages
A hero, three sections, an analytics tag, deployed. Builder writes it, previews it, ships it.
Built in · Personal
Builder. Build anything.
The main coding agent in Construct, for everything that lives outside the Construct platform — landing pages, websites, mobile apps, games, CLIs. Plans, codes, verifies, ships.
Screenshot needed
The Builder Space inside Construct. Center: a project plan being drafted (files, components, deploy target). Right: the running agent's status — current step, tool calls, verification results. Bottom right: a live preview of the work-in-progress. Hammer icon in the header.
/shots/space-builder.pngWhat it builds
Six things, to start.
Marketing websites
Multi-page sites with routing, content, SEO, and a CMS hookup if you want one.
Web apps
Vue, React, Svelte. Auth, data layer, deployment. Builder picks the stack to fit the brief.
Mobile apps
React Native, Expo, Tauri. Builds for iOS and Android — local preview, signed release flows.
Games
Phaser, three.js, simple 2D and 3D. From a prompt to a playable build.
CLIs and scripts
Node, Python, Bash. One-shots and recurring jobs. Tested, documented, runnable.
How it works
Plan, build, verify, ship.
Plans before it codes
Builder writes a plan first — files, dependencies, decisions. You review, refine, then it ships.
Verifies its work
Lint, typecheck, run tests, run a smoke check. Failures loop back into the plan instead of being declared done.
Multi-file edits as a diff
Changes across files arrive as a reviewable diff. Approve, revise, or roll back in one motion.
Deploys when ready
Pushes to your hosting of choice — Vercel, Netlify, Cloudflare, your own server. Or just builds locally if you prefer.