I sat through a Figma Config recap video expecting the usual pattern, a dozen flashy demos, half of which quietly disappear within a year. Config 2026 had that same flashy-demo energy, shader effects and 3D transforms included. But buried under the spectacle were two changes that will actually touch how I work every single day, and neither of them got the loudest applause in the room.
That's usually how it goes with these events. The features that generate the biggest gasps rarely turn out to be the ones your team adopts. Here's a version of the recap sorted by what changes your Tuesday afternoon, not what looked best on a keynote screen.
TL;DR: Figma Motion (a full timeline animation tool, shipped now) and expanded Agent capabilities are the Config 2026 announcements with the widest daily impact. Code Layers, Shaders, and Weave generative tools matter for specific workflows but won't touch most product designers' routine work (Figma Blog, 2026).
What Did Figma Actually Ship, Versus Promise?
Config keynotes always blur "available today" with "coming later this year," and it's worth separating the two before you plan anything around a new feature. Shipped now: Figma Motion, expanded Figma Agent (Skills, Connectors, visible team chats), and Shader fills built on existing shader infrastructure. Coming soon, no firm date beyond "later this year": Code Layers, Generative Plugins, Weave tools as a curated marketplace, and Agent expansion into FigJam and Slides.
If you're planning a Q4 workflow change around any of these, build your plan on what's actually installed in your account right now, not the roadmap slide. I've watched teams commit to a workflow redesign around a "coming soon" feature that slipped two quarters. Wait for general availability before you restructure anything.
| Status | Features |
|---|---|
| Shipped now | Figma Motion, expanded Figma Agent (Skills, Connectors, visible team chats), Shader fills |
| Coming soon, no firm date | Code Layers, Generative Plugins, Weave tools marketplace, Agent expansion into FigJam and Slides |
Why Does Figma Motion Matter More Than the Flashier Announcements?
Because it closes a gap nearly every product team has been patching with a separate tool for years. Motion brings a full timeline into the design file itself, keyframes, easing curves, spring physics, and it exports directly to CSS, JSON, React, and standard video formats for handoff.
I've watched designers hand off a hover animation as a Loom screen recording and a vague verbal description more times than I'd like to admit. That's not a handoff, it's a guessing game for whichever engineer picks up the ticket. A native timeline with exportable easing curves turns that into an actual spec, the same rigor spacing and color tokens already get, applied to motion for the first time inside the tool most teams already live in.
What Is Code Layers, and Should You Care Yet?
Code Layers, rolling out in July per Figma's own announcement, lets a designer turn any canvas layer into inspectable, editable code with one click, and lets a team pull an existing GitHub repository in as design layers for direct comparison against the design file. Dylan Field's framing at Config was blunt: "Code should be treated like any other design material."
That's a real philosophical shift, but the practical use case right now is narrower than the framing suggests. It's genuinely useful for auditing drift, spotting where a shipped product has quietly diverged from its design file, and for teams doing heavy design-to-code handoff who want a shared canvas rather than a Figma file plus a separate Storybook plus a separate spec doc. It is not, at least in this release, a general-purpose coding tool competing with Cursor or v0. Watch it, don't restructure your handoff process around it until it's out of "coming soon."
What Changed With the Figma Agent?
The Agent now ships to all users with two new concepts worth understanding: Skills, reusable packaged instructions for how your team wants the agent to work, and Connectors, integrations reaching into tools like Notion, Slack, GitHub, and Atlassian to pull context in or push updates out. Agent conversations are also visible to teammates by default now, rather than living in a private thread only the requester sees.
Is this worth turning on for your whole team immediately? Not all at once. Write one Skill well, test it on one real project, and see whether it actually captures your team's conventions before rolling it out portfolio-wide. A rushed Skill just teaches the agent your team's shortcuts and bad habits faster than a human would learn them.
What Should You Skip For Now?
Shader fills and 3D transforms, unless your daily work is marketing sites, launches, or portfolio pieces where visual spectacle is genuinely the point. For most SaaS product design, admin panels, forms, dashboards, these tools solve a problem you don't have this quarter. That's a fine reason to skip a feature. Not everything from a Config keynote needs to land on your roadmap the same week it's announced.
If you're picking two things to actually learn from this year's Config, make it Motion and one well-scoped Agent Skill. Everything else can wait for the version after "coming soon" actually ships, and you can revisit the Figma plugins worth your time list for tools that already earn a permanent spot in your toolbar today, no roadmap uncertainty attached.
