Figma makes its agent generally available and gives coding agents design context through Specs
On October 15, 2026, at its Config event in India, Figma announced new features for teams and agents: Specs, which carries design context to coding agents, opened in beta on paid plans, and code layers for code-backed prototypes opened in beta on every plan. The Figma agent that lives on the design canvas is now generally available.
A Config India release built for teams and agents
Co-founder and CEO Dylan Field announced the package in a Figma blog post dated October 15, 2026. The common thread is that agents now work on the design canvas next to people. Field's post refers to the Figma agent, embedded in the canvas, as now generally available; according to TechCrunch, the company had opened the agent to a wider user base the week before. Describing the quick, exploratory and slightly messy kind of making, Field gives that mode a name: "This is building to think."
The size of the event was part of the message. According to Figma, more than 30,000 people registered for Config India 2026, in person and online, which the company calls its largest international Config so far. At the same event Figma also unveiled an India-first MCP partnership with Sarvam.
Specs, code layers and two new layers for design systems
Specs is a multiplayer container that keeps context and decisions together on the canvas. Figma's own line for it is "Specs is where your design intent takes shape." Drop any .md file on the canvas and it becomes a spec; FigJam files, frames and other canvas nodes can sit inside it next to the text. Coding agents can pull a spec through the Figma MCP server together with everything it links to, such as frames, diagrams and code layers, plus any Code Connect snippets, and they can write updates back to it over MCP as the work moves on. Specs began rolling out on October 15 in open beta for paid plans on web, desktop and mobile.
Code layers lets teams build prototypes backed by code directly on the canvas, and it is now in open beta on all plans. Design systems get two additions. Guidelines, attached to published libraries, are meant to keep agents within established patterns and are in open beta. Code sources, in closed beta, can be pulled in from a GitHub repo or an npm package so agents can build and edit components and code layers. Figma says both will be offered on paid plans. Figma MCP also gains 20 new partner integrations; Figma's list includes OpenCode, Dia, Junie by JetBrains and Meta Muse. Finally, Payload, the open-source CMS, is coming to Figma Make. Figma notes that Payload downloads grew 6x over the past 12 months, and access is rolling out to all accounts in the coming weeks.
Code got faster, releases did not keep pace
Speaking to TechCrunch, Figma chief design officer Loredana Crisan said 17 times as many lines of code are produced now as before, while releases have risen only 1.3 times. In her account, much of that code is written to discover what the product should be rather than to ship. In our reading, that is why the package centres on context: agents can generate code quickly, but when knowledge about what to build and by which rules stays scattered, the output does not turn into shipped product at the same speed. Specs, Guidelines and Code sources all aim to put that knowledge where agents can read it directly.
The practical upshot is that the design tool is becoming the place where coding agents, and not only people, read brand and design rules. Teams that keep their brand guide and design system in a form agents can read will find it easier to stay consistent across AI-generated screens. We looked at how common agents have become in day-to-day work through an adoption report on August 27; Figma's release is the design-side counterpart of the same trend.
The sources do not mention Türkiye, so this section is commentary
None of the four sources mentions Türkiye. The announcements were made at an event in India, and the local partnership announced there targets India. This section is therefore not drawn from the sources; it is explicitly UNALSOFT's commentary.
Our view: the sources describe access to the new features by plan, not by region, with Specs and Guidelines tied to paid plans and code layers available on all plans. For a team working from Türkiye, the real questions are which plan it is on and whether its design system is organised in a way agents can read. The unknowns are worth listing one by one. The sources contain no partnership or event specific to Türkiye, no user figures for Türkiye, nothing on how teams in Türkiye would join the Code sources closed beta, and no assessment of how the agent handles prompts in Turkish.
UNALSOFT's take
We read this less as a tool update and more as a question of where design decisions live. When a page's colours, components and rules exist only in a visual file, an agent has to guess them; when the same rules sit in readable text and a published library, the screens an agent produces stay closer to the brand. That is why, in our web design work, we treat the design system and brand rules as a separate, readable deliverable. Because Specs, Guidelines and Code sources are still in beta, we suggest trying them on a small page before bringing them into the main flow of client work.
Is your design system organised so agents can read it?
A short conversation is enough to put your brand rules, components and page decisions into one source that people and agents both read.