Skip to main content

Figma adds agent workflows, canvas code layers and Specs

17 OCTOBER 2026·2 MIN READ·5 SOURCES

Figma announced features intended to bring teams, agents, design, code and context together in its creative canvas. The October 15, 2026 announcement included a new context container called Specs, code-layer prototyping and updates to agent integrations.

Figma adds agent workflows, canvas code layers and Specs

Key takeaways · 4

  • 01

    Check plan eligibility: Specs is rolling out in open beta for paid plans, while code layers are in open beta on all plans.

  • 02

    Specs can embed a FigJam file, a frame or any node from the canvas to combine project context.

  • 03

    Paid-plan users could create and edit code layers for free through November 4, 2026.

  • 04

    Figma says its MCP updates reduce errors and token usage, and announced 20 new MCP partner integrations.

A container for project context

Figma is launching Specs, a container for context on the Figma canvas.[2] A Spec can embed a FigJam file, a frame or any node from the canvas, and bring written intent, visual explorations and technical details together.[2] Figma says that context is meant to guide agents from prototype to production.[2] Specs began rolling out in open beta on web, desktop and mobile for paid plans.[2]

Prototyping with code on the canvas

Teams can explore and build prototypes backed by code on the canvas.[3] Figma says a supported, lightweight prototyping codebase can be imported from GitHub or a local folder, then used to build on screens and interactions.[3] Code layers entered open beta and are available on all plans.[1] On paid plans, creating and editing code layers was free through November 4, 2026.[3] The reported results were 30% faster iteration and feature development, and 50% less documentation, such as interaction specifications on tickets.[3]

Guidance and agent connections

Figma says files can help capture information agents cannot infer from library assets, including established patterns and anti-patterns.[4] Guidelines are available on Professional, Organization and Enterprise plans.[4] Figma also said code sources from GitHub repositories or npm packages can help agents build and edit components and code layers; that capability was starting in closed beta.[1] A system map helps track changes and dependencies.[1] Figma says its MCP updates reduce errors and token usage and help agents complete tasks more efficiently and reliably.[1] It also said teams could generate code layers and work with Specs from the AI tools they already use.[1]

Integrations and Figma Make

Figma said it was launching 20 new MCP partner integrations.[1] TechCrunch reported that Figma’s MCP supported more than 20 new tools, including Open Code, Dia, Grok Bot and Indian startup Sarvam.[5] Figma also brought Payload’s capabilities to Figma Make for creating, managing and shipping web apps.[1] The company says Payload lets marketing teams manage content without access to source code or engineers’ time.[1] Payload was available on all plans, with access rolling out to accounts over the following weeks.[1] Figma said Payload downloads had grown sixfold in the previous 12 months.[1] Separately, TechCrunch reported that Figma had made its on-canvas agent available to a wider user base in the preceding week.[5]

These features give product and engineering teams more ways to keep design context, prototype code and agent guidance connected in one workflow. Before adopting them, professionals should check which capabilities are in open beta, which plans include them and which are still in closed beta.

Why it matters
Daily session

Put this to work — one session a day, built for your industry.

Create a free account for a daily session — eight questions and one real-work challenge, on the news that affects your role.

Start free

How this developed

  1. 17 October 2026

    Figma adds agent workflows, canvas code layers and Specs

Sources

AI fluency, one session a day, built for your work.