Figma announces new features to define how agents work on its platform
- ID
- 35709
- Status
- summarized
- Published
- 15 Oct 2026, 12:30 PM
- Fetched
- 15 Oct 2026, 12:55 PM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/10/14/figma-announces-new-features-to-define-how-agents-work-on-its-platform/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 5.5
- Created
- 15 Oct 2026, 12:56 PM
- Tags
- Audience
- developersvibe_codersai_agent_users
What happened
At its first Config event in India, Figma announced Figma Specs, a Markdown-based editor where teams define a design language that both Figma's own agent and third-party agents can reference, with support for embedding FigJam diagrams, code layers, design libraries, code libraries and guidelines. The code layers feature, announced in private beta in June, moved to public beta, letting users ask the agent to turn a design into code or modify code to iterate on a prototype. Figma also added a Payload headless CMS integration, and said its on-canvas agent was made available to a wider user base in the past week.
Why it matters
If your team uses Figma with AI agents, the practical decision is whether design rules live in a versioned Markdown Specs file in the repo/canvas instead of being re-explained in each prompt - Figma is explicitly pitching Specs as the shared context source for agents, and code layers is now in public beta so you can test design-to-code iteration without a waitlist. The Payload integration matters if your design-to-site path runs through a headless CMS. Note the announcement gives no pricing, GA date, or Malaysia/SEA-specific availability details, so treat adoption as a trial, not a migration.
Discussion angle
Is a Markdown 'design spec' file the right contract for constraining agents, or does it just move the same ambiguity from prompts into docs - and does anything here actually help teams building outside the US/EU, given the event was Figma's first in India?