One protocol for your running app
Put a Figma-like interface over the application you already built. Vest watches the running app and turns visual edits into transparent, reviewable changes to its real source code.
Vest never re-renders your app. It observes the real runtime, maps what you select to source, and writes back a minimal diff.
Three core features
A design surface approachable for designers, backed by the source awareness, scope controls, and safe writes engineers need.
Click the running interface, see where its styles and components come from, and edit them in a familiar visual inspector. Designer-friendly on the surface; engineer-friendly underneath.
Change structure from the live app—not a mock. Insert components, remove elements, or duplicate existing components and data-driven items while Vest plans the corresponding source edit.
Use ready-made looks for headings, buttons, cards, backgrounds, and animations. Vest shows relevant presets and adds clean, removable CSS to your project.
Why Vest
Traditional design-to-code workflows split the product in two: a design file and the application people actually use. Vest starts with the existing, running project and treats runtime truth as the design material.
Vest observes the application your own development server renders. It does not reproduce your UI in a separate canvas or styling engine.
No Vest-specific starter, no migration, and no closed document format. Bring the codebase and toolchain you already have.
Runtime probes are adapters. The shared protocol resolves provenance, plans scoped edits, validates them, and writes through one safe path.
Your coding agent can use Vest's conventions to prepare components, styling, tokens, data-driven lists, and preset support.
Vest preserves formatting, previews wider edits, re-parses changes before writing, and rolls back instead of corrupting source.
Runtime support
Vest watches the application your runtime already renders. Framework-specific probes provide selection facts; provenance, edit planning, history, and undo stay shared.
Live DOM and Fiber-aware probe
Dart adapter with shared protocol
Static source adapter
Development-time injection
Webpack and Turbopack injection
Project analysis and preparation
The difference
Vest complements the tools teams already use while closing the gap between visual decisions and production code.
An AI code editor that moves from prompts or source to changes. Vest adds a visual, component-based canvas and maps every edit back to the real code.
Code → visualA collaborative design environment where design and production remain separate artifacts. Vest makes the existing application itself the design material.
One source of truthVisual editing for frontend code. Vest emphasizes an open, tool-independent change protocol and MCP preparation layer for existing projects.
Open protocol + MCPEarly development
Vest is taking shape in the open. Follow the repository for the protocol, runtime adapters, and first usable release.
Follow on GitHub ↗