Figma puts agent inside canvas

This is less a novelty demo than a strategic reframe: Figma wants the canvas itself to be the interface for AI, not a separate assistant panel.

• –The agent gets deeper design-system context than third-party tools, which should cut down on generic, off-brand outputs.
• –Bulk edits, component-state changes, and realistic content generation are the high-value use cases; that’s where an agent saves real time instead of just producing flashy mockups.
• –Keeping MCP as the code bridge while the agent stays on-canvas suggests Figma is separating design generation from design-to-code handoff on purpose.
• –Figma’s biggest advantage here is distribution: it already sits where teams review and iterate on product design, which is harder for standalone AI design tools to displace.