Figma Adds Version History for Generative Plugins and Shaders, With Agent-Written Change Logs

Figma announced on 27 October 2026 that editing a generative plugin or shader now creates a new version, and you can view and restore earlier ones. Each version gets an agent-generated description, which builds into a change log, and you can see which version is currently published. Figma says it is rolling out that week.

It sounds like housekeeping, and it is the kind of housekeeping that makes AI-built tools usable. Generative plugins and shaders are made by prompting the Figma agent, which means a small change in wording can rewrite a tool. Without versions, a good result could be overwritten by the next experiment with no way back. With them, you can try something bold and return to the last version that worked.

The developer documentation adds some detail. Updates through the MCP server require a commit message, and the tools accept an optional version parameter, a 40-character commit SHA, which defaults to the latest build. In other words, Figma is treating prompt-built tools like code, with commits and history.

Two other changes from the same week are worth noting. On 30 October Figma made internal publishing for Weave tools available on Organization and Enterprise plans, so a team can share a tool inside the company without publishing it publicly. The same day, connecting Google Drive to the Figma agent became available on all plans, including Starter.

For design teams, the lesson is about process. If you are building shaders or small plugins with the agent, treat them as assets with owners. Name versions sensibly, read the change log before publishing, and keep a note of what each tool is for. Version history only helps if someone is reading it.

We use Figma where it earns its place in our workflow, and the move towards proper history for generated tools is the right direction. Creative teams already know the pain of an overwritten file.