Figma code layers and Specs enter open beta

Figma’s October 15 releases bring code prototypes and collaborative Markdown documents onto its canvas, with MCP access for coding agents and specific beta conditions.

View sources
In this article
  1. Quick answers
  2. Prototypes join the canvas
  3. Specs gives the brief a shared home
  4. What to look for in a real handoff
  5. Sources & method

Quick answers

What are Figma code layers?

Code layers are interactive prototypes on the Figma canvas. Teams can import supported lightweight codebases from GitHub or a local folder and edit them with Figma’s agent.

Source 1

What does Figma Specs add?

Specs adds collaborative Markdown documents beside designs. Coding agents can read a spec and its linked context through Figma’s MCP server.

Source 2

Who can use the betas, and is code layers free?

Specs is rolling out to paid plans. Code layers is entering open beta and will use AI credits; creating and editing in it is free on paid plans through November 4, 2026, according to Figma’s announcement.

Source 1 Source 2

The practical takeaway

Code layers and Specs put working prototypes and written requirements in the same collaborative space; beta access and credits still matter.

Prototypes join the canvas

Figma moved code layers into open beta on October 15. Teammates can compare working prototypes on the canvas, extract editable design layers, and push changed code to a branch for review. The announced free editing period is temporary.

Source 1

Specs gives the brief a shared home

A second October 15 release, Specs, puts collaborative Markdown documents beside designs and diagrams. Figma says its agent can participate in comment threads, and coding agents can read a spec with linked context through Figma’s MCP server.

Specs is rolling out in open beta to paid plans across web, desktop, and mobile. A rollout announcement does not confirm that a particular account already has access.

Source 2

What to look for in a real handoff

Our analysis is that these additions could help a product manager, designer, and developer examine the same proposal. A working prototype can make an ambiguous requirement easier to discuss, while a written brief records why the team chose a particular behavior.

The test is whether those decisions survive implementation. Try a small flow with a success state, a failure state, and a recovery step. Ask a colleague to explain it using only the shared material, then compare the resulting implementation with the agreed behavior. That exposes missing context faster than judging how polished the first screen looks.

Both releases remain betas. We have not measured their reliability, compatibility with an existing project, or effect on a team’s delivery time. Treat the announced workflows as candidates for a contained trial.

Sources & method

Coverage of Figma’s October 15 product announcements with original analysis. We have not tested either beta; examples and capability descriptions come from Figma.

  1. Figma: Design together with code layers on the canvasPublished October 15, 2026
  2. Figma: Introducing Specs: Markdown as a mediumPublished October 15, 2026

Source pages reviewed October 16, 2026. Analysis and suggested evaluation methods are AI Toolcast’s own.

This article contains no sponsored placement or affiliate links.

Updated October 16, 2026 — added sourced answers distinguishing code layers from Specs and clarifying beta access and the temporary free editing period.