Figma used its first Config event in India, held in Bengaluru, to sketch out how AI agents should behave inside a design workflow. The headline launch is Figma Specs, a Markdown-based editor that acts as a native home for product context: teams can define their design language in plain text, either as a standalone file or alongside work on the canvas, and the document serves as a reference for both Figma's own canvas agent and third-party agents.
Specs is more than a text box. A document can reference elements on the canvas and embed FigJam diagrams, code layers and designs, and teams can bring in design libraries, code libraries and written guidelines so agents have a centralized source of context. Specs can also hand off to coding agents through Figma's MCP server, be used to seed new generation directions, or be built up into high-fidelity PRDs and data reports. Figma is explicit about the goal: more predictable agent output, not guaranteed adherence.
Code layers, the feature that puts working code on the design canvas, moved from private beta - announced in June - to public beta across all plans. Teams can create a code layer by prompting the Figma agent, importing from a GitHub repository, or connecting a coding agent through MCP, then refine interactions by asking the agent to revise specific parts. Extract designs turns any screen back into editable Figma frames, and finished work can be pushed to a branch and opened as a pull request. Creating and editing in code layers uses AI credits, and is free on paid plans through November 4, 2026.
The surrounding system-management tooling is expanding too. Design system guidelines are in open beta on all paid plans, letting teams publish the patterns agents should follow; code sources can be imported from a GitHub repository or an npm package in closed beta. A new centralized hub gathers the libraries that make up a design system, with a system map tracking changes and dependencies and a system check scanning for gaps such as missing descriptions and interactive states.
The ecosystem grew in parallel. Figma added support for more than 20 new tools over MCP, including Open Code, Dia, Grok Bot and the Indian AI startup Sarvam. Payload, the open-source headless CMS Figma acquired last year, is being integrated with Figma Make so generated sites can manage real content; the company said Payload downloads have grown sixfold over the past 12 months.
The framing from Figma's chief design officer Loredana Crisan captured why the company is pushing this now: "There are 17-times more lines of code being produced today than in the past. But when you're looking at releases, only 1.3-times more releases. A lot of that code actually is not necessarily built to ship, but really built to discover what the product is. It's built to design." CEO Dylan Field described the platform's next act as "a full-stack creative canvas where teams and agents can build together, from idea to ship, in a visual-first way."
India is the reason for the venue. Figma says the country is its largest user market outside the United States and that more than 40 percent of the top 100 BSE-listed companies use the platform, including Airtel, Swiggy, Zomato and TCS; more than 30,000 people registered for the event. Globally, about two-thirds of monthly active users identify as something other than designers and roughly 85 percent are outside the US. The announcements rolled out this week put Figma squarely in the same race as every other productivity platform: making agent output trustworthy enough to ship.
Comments (0)
Log in to join the discussion
Log InNo comments yet