Webflow has no undo. That is the fact sitting under every bulk idea you have shelved: the excerpt cleanup, the title-case pass, the rebrand sweep across forty collections. Handing an AI agent a live API key to a CMS you cannot restore is not a workflow, it is a dare. Goose is the agent built for people who think that way. It is open source, started at Block and now at the Linux Foundation's Agentic AI Foundation, it runs on your machine as a desktop app or a CLI, and it brings whatever model you choose. You can read every line of the thing you are about to trust. What it still needs is somewhere safe to work.
Scratch is that somewhere. It pulls your CMS collections down to a folder on your laptop, one file per item, and Goose does 99% of the work there, against files. The last 1%, what actually reaches the live site, stays with you. Every change comes back as a word-level diff, you approve what ships, and Scratch publishes only those items through the Webflow CMS API. The Designer never moves.
How it works
- Scratch pulls your collections into files. Every CMS item, page, and asset lands in a folder on your laptop, one file each, with an
AGENTS.mddescribing the layout. The Designer layout, components, and bindings never come down at all. - Goose edits the fields you point it at. Open the folder in Goose Desktop or
cdinto it and start a session. Goose reads theAGENTS.mdbriefing on startup, so it knows your collections before your first prompt. Rewrite every blog excerpt to one tight sentence and fix the title case. Goose works the files, never the live CMS. - You review every diff and publish. Scratch shows each change beside the original, word by word. Approve what ships, and Scratch sends only those items back through the Webflow CMS API. What you do not approve stays local.
What people use it for
The jobs that pile up because the Webflow editor opens one item at a time:
- Rewrite every blog excerpt to a single tight sentence, and settle title case across a whole collection.
- Backfill the SEO title and meta description on every case study that shipped without them.
- Carry a rebrand through a collection: the old product name out of body copy, headings, and SEO fields in one pass.
- Draft internal-link anchor text by letting Goose read the whole collection at once.
- Localize a collection into a second language, where Webflow exposes locales.
Run the first pass on a handful of items to settle the prompt, then point Goose at the full collection.
Why not an MCP server?
Goose speaks MCP natively. Its extension list is long, and wiring a Webflow server into it takes a minute. That minute is the problem: the publish step rides inside the tool call, so one confident autonomous pass ships across your whole collection, and Webflow gives you nothing to roll it back with.
Scratch keeps the access and moves the publish step. Goose gets the same full read and write an extension would give it, but against a local copy, and what writes back to Webflow is a separate, per-item decision that belongs to you. Goose can change anything. Only you can ship it. On a live site with no undo, that is the whole architecture.
What Goose edits in Webflow
- CMS collection items: rich-text, plain-text, slug, and custom fields
- Page metadata: title, slug, SEO and Open Graph
- Asset alt text
- Multi-locale content, where Webflow exposes it
Designer layout, components, bindings, and reference targets are never pulled into the folder. Ecommerce collections are out of scope. Validators flag length overruns, slug problems, and any field you tell them to watch, right next to the diff, so a bad rewrite announces itself before you approve it. The full field list is on Scratch for Webflow.
Questions people ask
Is this a Webflow MCP extension for Goose?
No. An extension wires Goose to your live CMS with the publish step bundled into the tool call. With Scratch, Goose's built-in file tools are all it needs: it edits a local copy, and publishing is a separate step that stays with you, one item at a time.
Will Goose touch my Designer layout?
No. Goose only ever sees content fields. Layout, components, bindings, and reference targets are never pulled into the folder, so there is nothing there for it to break.
Webflow has no undo. Am I stuck if a rewrite is wrong?
No. Scratch keeps the original beside every rewrite, and any published item can be rolled back per row, even though Webflow itself cannot do that. You decide which version stays.
Which model should I run Goose with?
Whichever you like. Goose runs no model of its own: bring an Anthropic, OpenAI, or Google key, reuse the Claude or ChatGPT subscription you already pay for, or run a local model through Ollama so the content never leaves your machine. Swap models between jobs without changing the loop.
Goose has an autonomous mode. Doesn't that make this riskier?
No, and that is the point of the architecture. Goose's permission modes govern how freely it edits the files, from ask-before-every-write to fully autonomous. Whatever mode you pick, publishing is not a tool Goose has. The gate to your live site sits in Scratch, after the agent is done.
Do I need to be a developer?
No. Goose Desktop is a normal app on macOS, Windows, and Linux: open the Scratch folder, type what you want done. The CLI is there if the terminal is where you live.
See it on your own collection
The fastest way to trust it is to watch it run on your content. Book a 30-minute demo on your Webflow CMS →, or try Scratch free and run the first pass yourself.