Launch
Caret
Visit
Example Image

Caret

Open-source AI design tool that lives in your repo

Visit

Your design shouldn't live outside your codebase. Caret gives your repo a design layer: real React in .caret/, rendered live on a canvas you can click and edit. Your app's source stays untouched until you sync.

Your design is the code. Not a picture of it, not a file that drifts. It lives in your repo, in git, reviewable in a pull request. So a fix you make once is still there tomorrow, instead of being regenerated away the next time you ask for something.

Sync is a thing you choose. When a design is ready, Caret works out what changed since the last sync and your agent makes the app match, in whatever framework you ship.

Use Caret with your own agent and harness. Designing happens in Caret, signed in with the AI coding plan you already pay for. Pushing those designs into your app can happen here too, or you can hand the sync to the agent in your terminal over MCP.

Free and open source, runs on your machine, no account.

Example Image
Example Image
Example Image
Example Image
Example Image
Example Image
Example Image

Features

  • Edit on the page: text, colour, images, and size, written to the file
  • Ask for the harder changes: paint a region, describe it in words
  • Three versions at once: generate, compare, keep one
  • Make the assets too: logos, photographs, textures, animated backgrounds
  • Sync into your app: in any framework, both directions
  • Bring your own model: a subscription you have, or an API key
  • Or hand the sync to your own agent: Claude Code and Codex work over MCP

Comments

Hi Everyone, Caret's product philosophy is that instead of having an external design tool that hosts design separately from the codebase, why not have the design artifacts themselves as code and have it tracked in the codebase? So that's why I created caret, now design and code lives in one place and drift between design and app layer is no longer existent.

Premium Products

Comments

Hi Everyone, Caret's product philosophy is that instead of having an external design tool that hosts design separately from the codebase, why not have the design artifacts themselves as code and have it tracked in the codebase? So that's why I created caret, now design and code lives in one place and drift between design and app layer is no longer existent.

Premium Products