Webflow Can Now Write Your Agent Instructions. Should You Let It?

What did Webflow actually announce about Agent Instructions?

At Webflow Conf 2026, held September 1 to 3 in Boston and online, Webflow announced that Agent Instructions can now be generated automatically inside Webflow, using context that already lives on your site. Webflow says the generation templates cover brand guidelines, design system, asset guidelines, and CMS content.

This is a smaller headline than Source, the composable operating layer Webflow put in limited research preview at the same event, and smaller than Campaigns, the new landing page product CEO Linda Tong introduced in the opening keynote. It is also, for most people reading this, the more immediately useful one. Agent Instructions are not a new product. Webflow says Agent Instructions launched earlier this summer, and that teams have been writing context files for design system documentation, SEO guidelines, form governance, and more. What changed at Conf is that you no longer have to start from an empty file.

Webflow describes the output as markdown files that can be edited, updated, or regenerated as your site evolves, and says Instructions generation started rolling out to everyone on the day of the keynote. I write these files by hand for client sites, so I have a fairly specific opinion about what a generated one is worth.

Why does an agent need instructions in the first place?

An agent with access to your site can change almost anything quickly. What it cannot do is guess the rules nobody wrote down. Agent Instructions are context files that tell the agent how your design system gets applied, what your brand sounds like, and which decisions are not its to make.

Think about what happens when a new contractor joins a project. They can write clean code on day one. They still ship the wrong thing in week one, because they do not know that the legal team signs off on every pricing claim, or that the h2 style on the blog template is deliberately different from the one on service pages. You fix that with onboarding, not with better talent.

Agents have the same gap and none of the social instinct to ask. A model given access to a Webflow site will happily create a new class called heading-2-blue rather than reuse the one you already have, because creating is cheap and reading your existing system is work it was not told to do. The instruction file is where you tell it that reading comes first.

What can Webflow generate, and what is still on you?

Webflow says the templates pull from what Webflow already knows about your site to cover brand guidelines, design system, asset guidelines, and CMS content. That maps well to the things Webflow can observe directly: your classes, your variables, your collection structure, your asset library.

Everything Webflow can observe, it can describe. Everything it cannot observe is still your job, and that is the half that prevents the expensive mistakes. Webflow does not know that your founder hates the word seamless. It does not know that the case study collection has three items that legal asked you to keep out of the sitemap. It does not know that your pricing page copy was negotiated line by line with a customer who reads it every quarter.

So I treat generation the way I treat a transcript. It removes the typing, not the thinking. A generated design system file is a genuinely good starting draft, because describing forty class names accurately is tedious and error prone when done by hand. A generated brand guidelines file is a starting draft that will read like a polite summary of your homepage, which is not the same thing as your brand.

How does this connect to the rest of what Webflow shipped?

Webflow announced MCP 2.1 at the same keynote, which it says will be available to everyone later this month. The CMS querying change matters most here. Webflow says agents can now sort and filter on custom fields, search across reference fields, and page through results in a single request.

Webflow says agents could previously sort and filter on only a few CMS fields, and only if you knew the exact field name. Read those two announcements together and the direction is obvious. Agents are getting broader access to your content at the same time as Webflow is making it easier to constrain them. That pairing is deliberate, and it is the right order to do things in. I have written before about building a custom MCP server for Webflow client onboarding, and the single biggest failure mode was never the tooling. It was the agent doing something technically valid that no human would have chosen.

Webflow also announced Releases, a branching and staging workflow it says will be in beta later this year, and Agent Presence, which it says will be available for all customers later this month, showing where an agent is working live on the canvas. Instructions constrain what agents do before the fact. Presence shows you what they are doing during. The activity log tells you after. Three different layers, and you want all three.

Does this change anything for AEO and AI search?

Indirectly, yes. Webflow also announced content agents inside Webflow AEO that find topics where competitors get cited and you do not, then draft original content in your CMS. Webflow says AEO pulls data from ChatGPT, Claude, Gemini, and Perplexity. An agent writing content directly into your collections is exactly the case where a weak instruction file becomes a publishing problem.

Webflow published its own numbers on the underlying problem at the same event. It says it analyzed the websites of 2,000 companies and found the median company appeared in 16 percent of the AI answers they would want to be part of, and were cited in those answers only 6 percent of the time. Those are Webflow's own figures about a market it sells into, so weigh them accordingly, but the shape matches what I see in client audits. Most brands are absent from the answers, not badly positioned within them.

The risk is what fills that gap. A content agent with no voice constraints produces competent, forgettable pages that cite nothing specific and say nothing a person could disagree with. That is the kind of page AI engines summarize and move past. The instruction file is where you write down the things that make your content worth quoting, including which claims must carry a named source and which numbers you are never allowed to estimate.

What should go in the instruction file that Webflow cannot write for you?

The parts that carry judgment rather than description. Webflow can inventory what your site contains. It cannot tell an agent which of those things are allowed to change, or who has to approve it. I keep a short, blunt list of four sections for every client site, and it survives regeneration because I write it where generation does not reach.

First, the non-negotiables. Legal language, pricing claims, compliance wording, and anything a regulator or a customer reads closely. Write the exact sentence the agent must not paraphrase.

Second, the reuse rule. New classes, new components, and new CMS fields are the three things agents create too eagerly. In Webflow specifically, an orphaned field created through the API can be genuinely painful to clean up, so I say plainly that the agent proposes schema changes and never makes them.

Third, the voice rules that are actually rules. Not be conversational, which means nothing, but the specific bans and the specific requirements. Named sources on every statistic. No invented client results. First person, never the corporate we.

Fourth, the escalation line. What the agent should stop and ask about rather than decide. For me that is anything touching pricing, anything that would change a live URL, and anything that deletes content.

Is a generated instruction file safe to ship as is?

No, and I do not think Webflow is claiming otherwise. Webflow describes generated files as markdown that can be edited, updated, or regenerated, which is the language of a draft rather than a finished artifact. Treat it that way and the feature is a clear win.

The specific failure I would watch for is confident description of an inconsistent system. If your Webflow project has three heading styles that drifted apart over two years, a generated design system file will faithfully document all three. The agent will then use all three, correctly, forever. Generation describes what is, not what should be, so the honest first step is reading the generated file to find out what your site actually looks like from the outside.

That alone makes it worth running. I have audited plenty of sites where the generated description would have been the first accurate inventory anyone had.

How would I roll this out on a real site?

Generate first, read carefully, then cut. Run the generation, read every file as a site audit rather than as documentation, and fix the underlying inconsistencies the file exposes before you accept it. A clean instruction file describing a messy system is worse than no file, because it teaches the mess.

Then add the judgment sections by hand. Non-negotiables, reuse rules, voice rules, escalation line. Keep them in clearly marked sections so a future regeneration does not quietly overwrite them.

Then test it the way you would test any process change. Give the agent a small, real task, watch what it produces, and add a rule for every surprise. This is the same discipline I argued for in writing an automation runbook before you ship. The document is not the deliverable. The behaviour it produces is.

Regenerate when the site changes materially, not on a schedule. Instructions that drift from the site are how agents learn confidently wrong things.

What should you do next?

If you run a Webflow site that agents already touch, generate the instruction files this week and read them as an audit. If your site is clean, you have saved yourself a long documentation afternoon. If it is not, you have just found the list of things to fix, written by something with no reason to be polite about it.

Then write the four sections nobody can generate for you. That is where the real protection lives, and it takes an hour, not a sprint. If you want to see how this fits alongside the bigger platform shift, I wrote about what the Source launch means for marketing teams as well.

If you are setting this up and want a second pair of eyes on your instruction files, or you want help getting a Webflow site into a state worth documenting, reach out. I am happy to look at what you have.