Questions, answered

An AI-native design layer summoned into your coding session: a code-first infinite canvas, a living design system in your repo, and governance (coverage, drift, promote) on top. Not a Figma replacement and not a one-shot code generator.

Figma's artifact is a design file you rebuild in code. Front End's artifact is the code — the canvas renders the live page. Many teams keep Figma for exploration; Front End keeps the system in git aligned with what ships.

Make is strong at fast prompt → preview inside Figma. Front End is built for design memory and governance while agents ship your repo: drift visible, off-system work promotable, canvas as a map of the whole product in code. Make wins the sprint; Front End wins the marathon.

The real thing. Frames render the live code document, so what you see is what ships — including responsive behavior and interaction states, not a static mock.

Yes. Import parses HTML/CSS into governed pages, captures styling into tokens and components, and surfaces where the systematized render matches the source and where it drifts.

Yes. Front End is an MCP server you register in your project (npx @thefrontend/connect). Summon it when you need alignment, the canvas, or capture — you stay in Claude Code and your repo.

v1: We ship for Claude Code first. It's a standard MCP server, so other MCP-capable hosts (e.g. Cursor, VS Code) can work once registered — we're testing those next. See Works with (v1). Sandboxed agents that block outbound network can't reach the hosted engine.

Yes — but not from this marketing site. After you connect, open your project in the canvas, click Share preview, and send the link. It's a frozen snapshot of that page (not live code). Team comments on that link are still in development. You need the tool + account running locally or on our hosted app when that's live.

Sign up free, copy your key, then run npx @thefrontend/connect <your-key> in your repo. Start free · How it works

Your code plus frontend.manifest.json (tokens, registry, pages). No proprietary engine source — the engine runs remotely.

Licensed access to the hosted engine: alignment, capture, and (on higher tiers) team governance. Not a downloadable UI kit. Pricing

Your repository and manifest stay yours. Engine calls stop when the subscription ends.

No. Agents only modify your pages, tokens, and registry — never the tool. See Agent Integrity.