The kindness that became a cage

In 2012, designer and researcher Bret Victor stood on a stage and demonstrated something that felt like the future. Code changed on one side of the screen. The program updated instantly on the other. No compilation. No waiting. The creator and the creation were in the same room.

His principle was simple: creators need an immediate connection to what they create. When that connection breaks, something important is lost.

Vlad Magdalin, who would go on to co-found Webflow, was in the audience. He built an entire company on that idea. Give designers direct control. Let them build websites by working with websites, not by working with code.

This week, Webflow published something unusual: an honest admission that they had not fully honored the principle they were built on. Their visual canvas was creating an internal representation that compiled into the actual HTML, CSS, and JavaScript users received. Two representations. One translation layer. And as they put it: "any system with two representations joined by a translation layer will drift."

The sentence that followed is the one I cannot stop thinking about.

"Hiding code stops being a kindness and starts being a cage."

That sentence is about Webflow's architecture. But it is worth understanding exactly what they are doing about it, and why now.

Webflow is rebuilding its platform so that the canvas and the shipped code are the same thing. Not a visual layer that compiles into code. The code itself, as the canonical source. What a designer creates and what users receive will be identical. The translation layer disappears.

The reason this is happening now is AI agents. Over 30% of Webflow's enterprise customers already use agents that read and write their websites directly through the Model Context Protocol. When AI can work fluently with real code, hiding it from those agents stops being a kindness. It becomes a limitation. The abstraction built for human designers becomes an obstacle for agents that need access to the actual thing.

This is the shift Webflow is responding to. And it surfaces a question that extends beyond any single platform.

Most digital environments are built the same way. A layer designed to make something accessible ends up sitting between the organization and the actual thing. The CMS that was built so editors could work independently is now so customized that only the agency can touch it. The analytics setup simplified into a dashboard is measuring the wrong things and nobody is quite sure how to change it. The brand system that lives somewhere between a PDF, a shared drive, and the designer who left last year.

Each of these was a kindness. A way to protect people from complexity.

At some point, the protection became the problem.

For organizations building on Webflow, the shift toward code as the canonical source is worth understanding now. It is not just a platform change. It is a signal of where digital systems are heading. The environments that age well are the ones where the source of truth is accessible, auditable, and not buried behind a layer that only one person knows how to navigate.

The question is simple, but not always easy to answer: do you know where the actual thing lives?

Not the dashboard. Not the export. The source.

References

• Webflow: Getting to the source. August 2026. https://webflow.com/blog/getting-to-the-source
• Bret Victor: Inventing on Principle. CUSEC, 2012. https://www.youtube.com/watch?v=PUv66718DII