Webflow unveils Source, giving AI agents governed access to marketing-site code

On September 2 at Webflow Conf 2026, the company introduced Source, a platform where marketers, designers, developers and AI agents are meant to work on one website through different governed views.

The announcement pushes beyond the familiar visual-site-builder boundary. Webflow plans to make code the common foundation, give agents access to it and let non-engineering staff retain visual control.

Source cannot yet be assessed as a finished mass-market product. Webflow calls it a limited research preview, so the news establishes a product direction and a proposed publishing model rather than proven website-production speed.

Source introduces Views, workspaces tailored to a participant’s responsibilities. A marketer could see campaigns and page variants, a developer could see code and releases, and an agent could be confined to the permitted portion of the work.

As CMSWire reported, governed code access is central to Webflow’s proposition. That matters more than generating a page from one prompt: once an agent can modify a real project, roles, review and release history become essential.

Webflow also announced Campaigns for landing pages and ad variants, Releases for branching an entire site, and Agent Presence for showing agent activity on the canvas. Campaigns is in beta and is due to become a paid product later; Agent Presence is promised later in September.

Those different statuses matter. They prevent the presentation from being treated as one already available suite. A team selecting a platform today still needs to verify each feature’s availability, price, permissions and rollback behaviour.

In Forbes reporting, Webflow chief executive Linda Tong described Source as an orchestration layer for continuous collaboration between people and agents. The more an agent can change independently, however, the more important the boundary between preparation and publication becomes.

A working site needs more than plausible copy. A change must survive checks for brand, responsive layout, forms, analytics, search indexing and accessibility. That is why site branching and visibility into agent work look more consequential than generation itself.

A migration decision is premature while Source remains closed. A more useful exercise is to list real operations: who changes a page, who approves it, which systems receive data, how a previous version returns and which actions an agent must never perform.

Webflow Conf ran from September 1 to 3 in Boston and online. The next meaningful evidence will not arrive on stage but in the access terms and in Source’s behaviour during conflicting edits and a faulty release. Those details will determine whether it becomes a production system or remains a convincing preview.