Two major announcements landed recently. Google rebuilt Stitch into an AI-native canvas, with voice interaction and deep integration with coding agents. Figma opened its canvas for agents to write to: skills files, the use_figma tool, and design systems as the intelligence layer for agentic authorship.
Both are serious pieces of engineering. Neither reaches the right destination.
The destination is a single interface. Somewhere design intent and working reality are the same thing. Not a translation or abstraction. Not handed off. Not an artifact rendered just so someone can look at it before converting it back into code.
The canvas must be a live interface into the system. Visual fidelity and code fidelity in the same artifact.
The technology exists. This isn't a capability problem. It's an incentive problem.
Figma's business depends on the canvas being the place where product decisions happen. Now that agents can write to it, using your design systems, it's genuinely capable infrastructure. But the pipeline hasn't changed: define intent, write to canvas, then implement in code. It's a round trip with a canvas detour in the middle.
Google's Stitch is more nuanced. It can generate real, usable code as a first-class output. The canvas is a generative workspace, not the end state. The direction is less wrong. But Stitch still starts from the canvas. And Google's underlying objective is primarily Gemini adoption, with the canvas as an on-ramp to Gemini CLI. A different destination.
Webflow has had the right direction for longer. It has always treated the canvas as an interface to real code. But its answer works for marketing sites, not functional applications. It stops before you reach real state, real data, and real complexity.
There's a real opening for a canvas-quality visual interface over a real application codebase.
Design systems and the broader product context become an execution layer: not documentation to be interpreted, but structured intent that can be delivered against. [Tempo](https://www.tempo.new/) is building that at the React codebase level. At Knapsack we're building the layer underneath — the place where the design system and broader context become the intelligence agents work from. Ingested, normalized, orchestrated, and prioritized. The canvas is a live view into what's actually running.
The companies with the most resources to build this have the most to lose from its existence.
That opening won't stay open forever.
