Skip to main content

Versions & Releases

Two ways to get your tokens out of Bezel: download or publish.

Download​

The download icon in the app header exports your current project state as a design-tokens.json file, right now. No version is created, no history saved. It's whatever your tokens look like at this moment.

Good for quickly sharing with someone, testing in a local build, or grabbing a working copy without ceremony.

Publish a release​

Publishing creates a versioned snapshot with a number like v0.1.0 and optional release notes. Every release is stored in your project history, so anyone with access can come back later, see what changed, and download that exact version.

Good for developer handoffs that need a stable reference, and for marking milestones. A repo can pin a release by setting its version in bezel.json version, so the MCP server syncs exactly that release.

Publishing requires Pro or higher. Without it, the publish button and version link don't appear in the header.

Publishing and your app​

Publishing a release saves a snapshot in Bezel. To use those tokens in your app, download the file or sync it with MCP, then run Bezel Kit. See Code.

Where to go next​