Build

AI-powered Cloudflare Workers builder.

#What Build does

A Cursor-style editor inside your workspace: Monaco, an AI grounded in your design tokens, live preview — and one-click deploy to your own Cloudflare account.

  • A real editor, in the workspace. Monaco — the editor behind VS Code — with a file tree and multiple files per project. HTML, Workers and React projects.
  • AI grounded in your brand. Build AI reads the selected design system's tokens and rules before writing — exact colour values, radius, fonts. Token-aware output, not guesses.
  • Pick your Claude, per project. Haiku for quick edits, Sonnet for balanced work, Opus for heavy refactors — chosen per project, billed through Cloudflare, with prompt caching cutting repeat costs.
  • Live preview as you build. HTML and React projects render inline in a Code | Preview tab — the AI streams changes file by file and you watch them land.
  • Deploy to YOUR account. One click uploads the Worker to your own Cloudflare account and returns the live workers.dev URL. Status and worker name live on the project card.

#From new app to deployed

  1. Click New app and choose a framework: HTML, Worker or React (Astro/Next.js via CF Containers is on the roadmap and blocked server-side until then).
  2. Work in the editor: Monaco with a file tree on the left, your code in the middle, Build AI on the right.
  3. Pick the AI model per project — Claude Haiku 4.5, Sonnet 4.6 or Opus 4.8 — and select a design system to ground the AI in your tokens and rules.
  4. Describe what you want; the AI streams changes file by file and applies them. HTML/React projects render live under the Preview tab.
  5. Click Deploy: the Worker is uploaded to your own Cloudflare account and the live workers.dev URL comes back. Status and worker name land on the project card.

#On the MCP surface

Build's AI is the in-editor pair — and your own MCP-connected AI (Claude Code, for example) curates everything it builds on: the design tokens, the components, the wireframes. One platform, full context on both sides.

#On the Cloudflare side

  • Deploy uploads the Worker to YOUR Cloudflare account via your own OAuth token — the live workers.dev URL belongs to you, and every deploy is recorded with status and worker name.
  • Previews resolve your account's own workers.dev subdomain; AI usage is billed through Cloudflare.