Figma is sharpening its position in the frontier AI race with a new set of product features designed to define how agents work across its platform, while also opening its code layers feature to broader testing. The announcements signal a more deliberate strategy: rather than treating AI as a bolt-on assistant, Figma is trying to establish the rules, structure, and permissions that govern how intelligent systems participate in design and development workflows.
Agent Workflow Controls
The company's latest update centers on the mechanics of agent behavior. In practical terms, that means Figma is not only adding AI capabilities, but also specifying how those capabilities should operate within the product's collaborative environment. That distinction matters. As AI agents become more capable of taking actions on behalf of users, software platforms are increasingly being forced to answer a difficult question: who controls the agent, what can it access, and how does it behave in shared workspaces?
For Figma, the answer appears to be a framework that makes agent activity more predictable and more useful for teams. The company's approach suggests it wants agents to function as structured collaborators rather than free-roaming automation tools. That could help address a major concern in enterprise software adoption, where security, auditability, and role-based permissions often determine whether AI features are embraced or sidelined.
The timing is notable. Across the technology sector, product leaders are racing to define agentic interfaces before those interfaces become standardized by competitors. In that context, Figma's move is as much about platform architecture as it is about product features. By setting the terms of engagement now, the company may be trying to make its environment the default workspace for teams that want AI assistance without losing control over design integrity or workflow governance.
Code Layers In Beta
Alongside the agent-focused update, Figma is releasing its code layers feature in open beta. The feature is designed to bring code more directly into the design experience, reinforcing Figma's long-running effort to narrow the distance between what teams design and what engineers ultimately ship.
Open beta access is strategically important. It allows Figma to gather feedback from a wider set of users while signaling confidence that the feature is ready for real-world testing. More broadly, code layers fit into a larger industry trend in which design tools are evolving into execution environments. The goal is no longer simply to mock up interfaces, but to support a workflow where design artifacts can map more cleanly to production code.
That convergence has implications for both designers and developers. Designers gain a more tangible connection to implementation, while developers may benefit from fewer translation errors between visual intent and code output. If the feature works as intended, it could reduce friction in product teams that have historically relied on handoffs, rework, and interpretation across disciplines.
Figma's Platform Ambition
The combination of agent controls and code layers points to a broader strategic ambition: Figma wants to be more than a design application. It is positioning itself as a system where creative work, technical execution, and AI assistance coexist under one roof. That is a meaningful shift in a market where the most valuable software platforms are increasingly those that can orchestrate multiple stages of the product lifecycle.
This also places Figma in direct conversation with the broader frontier AI ecosystem, where the most consequential products are not necessarily the ones with the most powerful models, but the ones that can embed intelligence into everyday workflows in a safe, scalable way. In that sense, Figma's latest release is less about flashy AI and more about infrastructure: the rules, interfaces, and permissions that make AI usable inside a professional environment.
The company's challenge now will be execution. Agentic systems can create efficiency, but they can also introduce complexity if their behavior is opaque or difficult to manage. Likewise, code-to-design features must prove they can improve collaboration without adding another layer of abstraction. Still, by moving on both fronts at once, Figma is making a clear statement about where it sees the future of product development heading: toward integrated, AI-aware workflows that blur the line between design and delivery.