Figma launches Specs — a multiplayer Markdown container on the canvas in open beta for paid plans, where agents like Codex can read your spec through the Figma MCP server and code layers move to open beta

2 sources

On October 15, 2026 (the page's JSON-LD datePublished reads 2026-10-15T04:51:00Z), Figma announced: "We're launching Specs, a container for your context that lives on the Figma canvas." — "Turn existing Markdown into a spec by dragging and dropping any .md file onto the canvas." — "It's the de facto format for sharing context." The framing: "That's why we built Specs: a multiplayer container that allows context to fully express itself and move into, out of, and across Figma." Creation: "To create a spec, just press 'D' on your keyboard or click the Specs icon in the toolbar in Figma or FigJam." Agents: "And since the Figma agent can read and reply to comments, you can collaborate with the agent the same way you would with a human collaborator." MCP: "MCP now reduces errors and token usage so teams can move faster and more efficiently." — "20 new integrations bring Figma context and capabilities into more of your tools." — "Through the Figma MCP server, agents like Codex can read a spec and see all of the context it links to." Availability: "Specs is available on web, desktop, and mobile, rolling out in open beta to paid plans starting today." Per TechCrunch (Ivan Mehta, byline 9:30 PM PDT October 14, during "the company's first Config event in India"): "Figma also made its code layers feature available to users in open beta" — "The company announced this feature in private beta back in June." — and MCP support is "supporting over 20 new tools with its MCP, including Open Code, Dia, Grok Bot, and Indian AI startup Sarvam". Chief design officer Loredana Crisan told TechCrunch: "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…"

Why now

The context your agents read just got a home on the canvas. Per Figma's post, "We're launching Specs, a container for your context that lives on the Figma canvas." — and the entry path is zero-friction: "Turn existing Markdown into a spec by dragging and dropping any .md file onto the canvas." Second layer, the agent loop is the story: per the post, "the Figma agent can read and reply to comments, you can collaborate with the agent the same way you would with a human collaborator" — and the handoff runs "Through the Figma MCP server, agents like Codex can read a spec and see all of the context it links to." Third layer, the ecosystem moved the same week: per TechCrunch, "Figma also made its code layers feature available to users in open beta" — private beta back in June, per the outlet — and MCP is "supporting over 20 new tools with its MCP, including Open Code, Dia, Grok Bot, and Indian AI startup Sarvam". Fourth layer, the why-now framing is Figma's own executive: per TechCrunch, Loredana Crisan says "We see Figma as the place where software teams come to decide what they build and ship." — with her figures of "17-times more lines of code being produced today than in the past" against "only 1.3-times more releases".

Why it is worth publishing

The most workflow-relevant card of the day for creators who build with agents: the spec-as-context pattern — write the plan in Markdown, pin it next to the designs, and let the coding agent read it through MCP — is a demo your audience can copy for free-form use in any stack. The differentiation play is the state discipline: Specs is "rolling out in open beta to paid plans" per Figma's post, code layers is its own open beta per TechCrunch, the MCP counts stay per-outlet (Figma's "20 new integrations" versus TechCrunch's "over 20 new tools"), and the 17-times/1.3-times figures are Crisan's own characterization told to TechCrunch. Creators who keep every state and number labeled own the spec-workflow beat; everyone else will write 'Figma goes GA', which no source says.

Evidence basis

Two opened sources: Figma's official blog post (JSON-LD datePublished 2026-10-15T04:51:00Z — the page carries no article:published_time meta, so the JSON-LD block is the mechanism carrying the stamp; opened and read in full, with the contiguous agent-comment sentence verified against the page's embedded JSON payload after flat extraction interleaved a sibling-post promo card mid-sentence) and TechCrunch (Ivan Mehta, byline 9:30 PM PDT October 14, Wednesday calendar-verified; article:published_time meta 2026-10-15T04:30:00+00:00 — the same moment in UTC; opened and read in full). Calendar checks: October 15, 2026 = Thursday; October 14 = Wednesday; October 16 (this card's publish date) = Friday. Layer discipline: the 20-integrations count (Figma's page) and the over-20-tools rendering with named tools (TechCrunch) stay per-outlet; the code-layers open-beta fact rides TechCrunch's own article — the 'Today, code layers moves into open beta' sentence on Figma's page sits on a promo card for the sibling post; the private-beta-in-June history is TechCrunch's; the 17-times/1.3-times figures are Crisan's own characterization — the claim quotes her unit in full to its true end and summary layers excerpt with an ellipsis. Availability: 'rolling out in open beta to paid plans' — the beta state and paid-plan gating stay attached everywhere; 'starting today' stays anchored to October 15 inside attributed quotes; the India-event framing stays TechCrunch's.

“Figma's new Specs makes your Markdown a multiplayer container on the canvas — drag in any .md file, and agents like Codex can read it through the MCP server (open beta, paid plans).”

Angle

Frame it as 'specs just became the interface between your team and your agents' in three beats. Beat one, the container: per Figma's post, drag any .md file onto the canvas or "press 'D' on your keyboard" to start a spec that embeds FigJam files, frames, or any node — show the drag-and-drop live. Beat two, the agent loop: per the post, the Figma agent "can read and reply to comments" in a spec, and "agents like Codex can read a spec" through the Figma MCP server — hand one spec to a coding agent on camera. Beat three, the state map: per the post, Specs is "rolling out in open beta to paid plans starting today" (October 15); per TechCrunch, code layers separately moved to open beta after private beta in June — keep every beta label on screen, and keep the 17-times/1.3-times figures labeled as Crisan's characterization told to TechCrunch.

Format

Long-form explainer

Demo idea

A spec-to-code walkthrough: draft a small PRD spec on the canvas (press 'D'), embed a FigJam flow, drop in an existing .md file, have the Figma agent reply to an open comment, then paste the spec link into a coding agent via the Figma MCP server and show what it builds — closing with the state map: open beta, paid plans, per Figma's post.

Platform notes

Specs availability: "rolling out in open beta to paid plans starting today" (October 15, per Figma's post) — open beta and paid-plan gating stay attached; never 'GA', never free-tier access, and 'starting today' never repeats as the card's own voice. Code layers is a separate feature with its own open beta (per TechCrunch, private beta since June) — never collapsed into Specs' launch state. MCP counts stay per-outlet: Figma's "20 new integrations" versus TechCrunch's "over 20 new tools" with Open Code, Dia, Grok Bot, and Sarvam named. The 17-times/1.3-times figures are Crisan's characterization told to TechCrunch — attributed every time, never Figma-official metrics. "agents like Codex" is the post's example, never a claim that every coding agent integrates. 'First Config event in India' is TechCrunch's framing. zh scripts keep Specs, code layers, MCP server, Figma Make, Payload in English, write 公开测试（open beta）never 正式上线, and render the 17-times figure as 约为过去的 17 倍, never 多用约 17 倍.

Usable claims

On October 15, 2026 (the page's JSON-LD datePublished reads 2026-10-15T04:51:00Z), Figma announced Specs. Per Figma's post: "We're launching Specs, a container for your context that lives on the Figma canvas." — "Turn existing Markdown into a spec by dragging and dropping any .md file onto the canvas." — "Today, more and more product builders are working in Markdown, as collaborating with agents becomes more standard. It's the de facto format for sharing context." The framing: "That's why we built Specs: a multiplayer container that allows context to fully express itself and move into, out of, and across Figma." Creation: "To create a spec, just press 'D' on your keyboard or click the Specs icon in the toolbar in Figma or FigJam." On agent collaboration: "And since the Figma agent can read and reply to comments, you can collaborate with the agent the same way you would with a human collaborator." On MCP: "MCP now reduces errors and token usage so teams can move faster and more efficiently." — "20 new integrations bring Figma context and capabilities into more of your tools." — "Through the Figma MCP server, agents like Codex can read a spec and see all of the context it links to." Availability: "Specs is available on web, desktop, and mobile, rolling out in open beta to paid plans starting today." Per TechCrunch (Ivan Mehta, byline 9:30 PM PDT October 14, during "the company's first Config event in India"): Figma debuted "Figma Specs, which is a markdown editor that lets users define their design language in a simple way", and Specs "can exist as a standalone file in Figma or can co-exist within the canvas"; "Figma also made its code layers feature available to users in open beta" — "The company announced this feature in private beta back in June."; and MCP support is "supporting over 20 new tools with its MCP, including Open Code, Dia, Grok Bot, and Indian AI startup Sarvam". Chief design officer Loredana Crisan told TechCrunch: "We see Figma as the place where software teams come to decide what they build and ship. And so for that, I think one of the key things to keep in mind about what AI has changed and what it made available is the ability to build," — and her closing span: "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."

Evidence pipeline

From the news

Breakdown

A design-tooling story where beta state and attributed metrics are the content. Layer one, the state discipline: "Specs is available on web, desktop, and mobile, rolling out in open beta to paid plans starting today." — the open-beta state and the paid-plan gating stay attached in every layer, 'starting today' stays anchored to October 15 inside attributed quotes, and the card never writes Specs as generally available or as free-tier access. Layer two, code layers is a different feature with its own state: per TechCrunch it moved to open beta at the India event after "private beta back in June" — and the 'Today, code layers moves into open beta' sentence on Figma's page sits on a promo card for the sibling post, so the open-beta fact rides TechCrunch's own article, never the promo card. Layer three, the MCP counts stay per-outlet: Figma's page says "20 new integrations" while TechCrunch says "over 20 new tools" and names Open Code, Dia, Grok Bot, and Sarvam — the two renderings are never blended into one number. Layer four, the metrics stay attributed: "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…" is Loredana Crisan's own characterization told to TechCrunch — the claim quotes her unit in full to its true end, this excerpt ends with an ellipsis, and the figures are never Figma-official metrics or independent industry stats. Layer five, the agent scope: "agents like Codex" read specs through the Figma MCP server — 'like Codex' is the post's example, never a claim that every coding agent already integrates, and the Figma agent's read-and-reply behavior is about comments in Specs. Editor's rules: beta labels everywhere, per-outlet counts, executive-labeled figures, and an example kept as an example.

Sources

Risks

Before publishing, re-check each layer: the open-beta and paid-plan state stays attached to every Specs availability line; 'starting today' stays anchored to October 15; code layers keeps its own beta state via TechCrunch's sentence, never the promo card; the 20-versus-over-20 MCP counts stay per-outlet; the 17-times/1.3-times figures stay Crisan-attributed in total-multiple form; 'agents like Codex' stays an example; and the India-event framing stays TechCrunch's. If your script compresses any of these, cut the detail rather than round it.

Demo ideas

Spec-to-code walkthrough: press 'D', embed a FigJam flow, drop an .md file in, let the Figma agent reply to a comment, then hand the spec to a coding agent through the MCP server
State-and-source map card: Specs open beta (paid plans, per Figma's post) beside code layers' separate open beta (per TechCrunch), the two MCP counts per outlet, and the Crisan figures labeled as her characterization