Figma Make adds Plan mode, web search, and pinned comments

• figma's feature roundup says Make now has four new control layers: Plan mode, a messaging queue, web search and fetch, and pinned comments.
• According to Figma's release notes, Plan mode asks clarifying questions, drafts a plan before generation starts, and costs more AI credits than a standard build.
• Figma's Make editor docs add two workflow details the tweet skips: Plan mode is marked paid-plan only, and web search or URL fetch can pull live external information into a prototype.
• Figma's comments docs say Make comments capture a screenshot of the element's current state, which matters because every code change creates a new version of the app.

Figma's own docs are more revealing than the launch tweet. The release notes frame Plan mode as a checkpoint for complex builds, the Make overview positions web search and URL fetch as grounding tools for real-world data, and Matt Colyer's interview via Dan Shipper makes the bigger bet explicit: Figma wants AI creation to happen on the canvas, not inside a chat box.

Plan mode is an opt-in step before code generation. Figma's release notes say Make inspects the project, asks clarifying questions, then drafts a plan you can edit and approve before anything gets built.

The same notes say it is meant for more complex prompts, like multi-section layouts or detailed specs, and can be triggered from the prompt-box dropdown or with the /plan command. The Make editor docs also mark Plan mode as a paid-plan feature.

The new queue is basically a follow-up buffer. Figma's release notes say you can stack instructions while Make is still generating, then edit or delete those queued messages before they automatically send after the current build finishes.

That gives Make a more asynchronous rhythm than the usual prompt, wait, prompt loop. Figma is adding turns and checkpoints, not just faster generation.

Figma's Make overview says web search can pull current information into a prototype, while URL fetch can ground it with content from a specific page. The Make editor docs describe the same feature as bringing live external information into the app you are building.

That moves Make closer to a research-backed prototyping tool, not just a generator working off whatever context sits in the file.

Figma's comments docs explain why comments needed their own update in Make: every code change creates a new file version, so comments can end up referring to earlier states of the app. To keep feedback anchored, Make captures a screenshot of the selected element when the comment is placed.

Pinned comments fit that model. They give reviewers a stable reference point inside a prototype that keeps changing underneath them.

In Dan Shipper's interview post, Matt Colyer, Figma's director of product management for developers, argues that chat-based tools are the wrong interface for design. Shipper's summary says Figma's MCP server already supports two-way workflows, from reconstructing a live web page on the canvas to handing a Figma design to an agent for pull-request changes.

A second Figma product line moved the same day. figmaweave's Aleph 2.0 post shows Runway Aleph 2.0 landing in Weave for shot reframing, character swaps, and background changes without restarting from scratch.

Taken together, the week’s updates point in one direction: Figma is adding more review, grounding, and edit controls around generative output, whether the output is a prototype in Make or a scene in Weave.