Webflow Conf 2026: Source, Agent Presence, and a Shared Website Workflow

Webflow's September 2 conference announcements put collaboration between people and agents at the centre of its website strategy. The interesting change is the breadth of the proposed working environment: design, content, code and releases increasingly share a place where teams can inspect what an agent is doing.

Webflow's conference recap introduced Source in a limited research preview and described Agent Presence, expanded MCP access, and site-wide release staging. It also separated availability: Campaigns was in beta, Assets was due to enter beta in October, and Releases was planned for beta later in the year. Those distinctions matter when deciding what a client can actually use.

Imagine an agency preparing a product launch. A designer changes a reusable component, an editor checks the product claims, and an agent drafts several regional pages. The hard part is keeping those changes coherent. A generated page becomes useful when the people responsible for it can understand its structure, improve its design and include it in a controlled release.

Our reading of the announcement is that this handover is becoming a product concern. Teams need a shared understanding of the work in progress. They need to see which changes belong together and which decisions still require a person. A conversation with an agent is only one surface in that larger process.

This also changes the questions agencies should ask during evaluation. Does an agent's output remain editable through the tools the team already uses? Can another contributor inspect unfinished work? What happens when a designer and an agent touch the same component? A convincing demonstration should answer these with a real project, not only a successful prompt.

Webflow describes Agent Presence as a way to show an agent working on the canvas, and Source as an environment connecting code and the marketing stack. Its conference recap presents broader MCP querying and deployment work alongside these interfaces. The direction is a website workspace where agents become visible contributors.

Visibility is valuable, but a team still needs an operating policy. Seeing an agent move through a page does not itself prove that a proposed change is accurate, accessible or ready to publish. The practical process should name the reviewer, the permitted task and the expected result before work begins.

For a small campaign, that might mean a marketer accepts the copy and a designer checks the responsive layout. A larger launch may need coordinated review across content, components and regional requirements. The process should fit the change rather than placing every task behind the same ceremony.

The conference recap mixes shipping updates with previews and future releases. A procurement or implementation decision should therefore begin with the specific feature and its current access conditions. Request a demonstration in the workspace and plan the team will use, then check the release notes before committing a delivery schedule.

The broader industry signal is clear: website platforms are designing for people and agents working together throughout a project. That is a more substantial development than adding a text generator to an editor. Its value will be measured in understandable changes, smooth review and websites that remain pleasant for the team to maintain.

The conference announcement was followed by a more concrete MCP product update on September 21. MCP, or Model Context Protocol, connects an assistant to a system's exposed tools. Webflow describes native GSAP-powered interactions that remain editable in its visual panel, richer CMS queries with custom-field and reference-field filtering, and Webflow Cloud deployment, status and debugging operations. Secrets and environment variables remain in the CLI rather than MCP. These documented capabilities should be evaluated separately from Source's research preview; one feature's availability does not establish the status of the whole announcement.

Start with one page built from approved components. Keep the existing live page available while the team reviews the proposed result. Check responsive layouts, forms, links, accessibility and the agreed copy before considering the pilot successful.

Then test the handover: can a designer edit the agent's work, can an editor see concurrent changes, and who is permitted to publish? Give the agent a defined scope and a clear point at which it asks for review. The useful outcome is a maintainable website and a controlled release, not merely a fast first draft. Our agent workflow explains this task-to-review rhythm, and the technology overview describes Progressive CMS's REST API, CLI and MCP surfaces.

Primary sources: Webflow Conf 2026 announcements and Webflow's September 21 MCP update. Facts checked on October 9, 2026; access conditions should be verified for the project you intend to use.

For another approach to agents working inside a CMS, read Storyblok Agents and scheduled AI workflows. For practical guidance on structured content, permissions and reviewed publication, see the agent field guide.