Figma has spent years building a review pipeline for the software that runs inside people’s design files. Plugins submitted to its community marketplace go through checks for quality and usability, for “trust and safety,” for business considerations and legal compliance, and developers are asked, though not required, to fill out a security disclosure form, according to Figma’s own plugin and widget review guidelines. It’s a modest system by enterprise-security standards, and Figma is candid that it offers no guaranteed turnaround, only a promise to be “thoughtful and reasonably prompt.” But it exists for a real reason: a plugin can read and modify a file, and someone has to vouch, at least loosely, that it won’t do so maliciously or carelessly. At Config 2026, Figma introduced a feature that makes that entire apparatus optional.
A tool for every problem, and no one to check it
Generative plugins, unveiled alongside a raft of other AI features at the conference, let a designer describe a tool in plain language and get a working piece of software in return. “To build a generative plugin, just describe the tool you need: the behavior, the controls and the parameters,” Figma explained in its Config 2026 recap, pointing to examples like layout generators and vector path tracers, tools that would previously have required someone who actually knew the plugin API, as TechCrunch reported from the same announcement. That’s a genuine unlock: the gap between wanting a small, specific tool and being able to build one has, for most designers, simply closed.
The catch is where these tools live relative to the review system Figma already has. A generative plugin built and used inside your own file needs no vetting whatsoever, and Figma doesn’t pretend otherwise, since the entire pitch is that a designer can go from prompt to working tool without ever leaving the canvas. Today, Figma says, “you can build something for yourself and share it with anyone in your file.” That’s already a meaningfully different trust boundary than the marketplace’s, since a file can be shared with a client, a contractor, or an entire cross-functional team, and none of those recipients has any signal that the tool they’re now running was ever looked at by anyone other than the person who typed the prompt. And the boundary is set to widen further: Figma says that “soon, you’ll be able to publish tools to your team, organization or the broader community,” language that implies the same disposable, unreviewed plugins will eventually flow outward at the scale the marketplace was built to police, just without the checks that came with it.
Figma has just built an easier way to create software that answers to no second pair of eyes at all.
What review is even protecting
The stakes of that gap are sharper because these tools are no longer confined to nudging pixels around a canvas. Figma’s Connectors, launched in the same wave of announcements, “let the agent reach the tools already in your stack — for example, Notion, Slack, Granola, Hex, GitHub, Atlassian and more — and then send updates back,” according to Figma’s own description. TechCrunch’s coverage describes Agent Skills in similar terms: designers “write text prompts to create repeatable skills that AI agents can use,” reaching into Notion, Granola, Excel, and GitHub. Put a generative plugin and a Connector-equipped agent in the same file, and “a little tool I made for myself” and “a script with write access to our GitHub repo” are no longer a distance apart.
Figma’s review guidelines were written for a world where a plugin author submits code once, to a marketplace, for scrutiny before wide distribution; they say plugins “must maintain similar standards” to Figma’s own on security and data protection and can’t touch a file “without explicit user consent.” None of that language anticipates a tool generated fresh from a prompt, used immediately, and shared with a file’s collaborators before anyone outside the prompt window has seen what it does. The review process doesn’t disappear, technically speaking, it simply stops applying to the growing share of tools that never touch the marketplace it was designed to gate.
None of this makes generative plugins reckless by design; most will be exactly what they look like, small conveniences that save a designer from writing a script or waiting on an engineer. But the logic of a trust-and-safety review rests on the idea that some tools are consequential enough to warrant a second pair of eyes before they run. Figma has just built an easier way to create software that answers to no second pair of eyes at all, and it’s rolling that out gradually and by default, ahead of any answer to the question its own review process was meant to settle.
