Figma turns Weave into a two-way canvas citizen

Weave comes to the canvas

Figma spent the week closing the loop between its agentic Weave workflows and the place designers actually work. You can now connect designs you've already created on the Figma Design canvas straight into Weave workflows, which means a workflow no longer has to start from a blank slate or a duplicated file — it can operate on the real thing. In the other direction, custom Weave tools can be published to the Figma Community so that you and anyone else can run them directly on the canvas in Figma Design. Together the pair reframes Weave from a side workspace into something that plugs into the canvas both ways: your existing designs flow in, and the tools you build flow out to other people.

Smaller quality-of-life work landed alongside it — folders now show a preview of their contents, which is the sort of change you notice only when you stop opening three folders to find the right one. Figma also pushed a maintenance and dependency release with routine fixes.

Loops learn to follow the work

Linear's story of the week is follow-through. Loops — its recurring agent workflows — previously ran on a fairly narrow set of triggers, but they now respond to changes across initiatives, projects, cycles, and issues. That matters because the hard part of a plan change is rarely the decision itself; it's the cascade of stale documents, unfiled issues, and people who didn't hear about it. Linear is positioning Loops to absorb that coordination: they can now edit Linear documents and draft and post Slack updates, so a project shift can ripple into the written record and the announcement without a human relaying it. The same update introduced callout components for issue and project descriptions and documents, and extended introductory Loops credits through the end of the year — a nudge for teams still deciding whether to build on them.

Quiet weeks for Notion and Slack

Notion shipped a run of bug fixes and performance improvements, a dependency update, and an internal release, none of which carry user-facing detail worth chasing. Slack, for its part, was candid that the week's work was invisible — paddling hard beneath the surface, gliding on top. Both are the kind of week that exists to keep the larger releases honest.