A Webflow cleanup has two moments where trust can break: while the agent is working, and when the changes go live. Most AI tools are opaque at the first moment and instant at the second, which on a CMS with no undo is exactly backwards. Pairing Antigravity with Scratch fixes both moments separately. Antigravity, Google's agent-first IDE, makes the work visible: the agent's plan unfolds in the editor, and every edit lands in a file you can open while it runs. Scratch makes the going-live deliberate: nothing reaches Webflow until you have read the diff and approved it.
The loop is plain. Scratch pulls your CMS collections down as a folder on your laptop, one file per item. The Antigravity agent does 99% of the work in that workspace, in plain sight. The last 1% is yours: word-level diffs in Scratch, approval per item, publish through the Webflow CMS API. The Designer never moves, and neither does anything you have not signed off on.
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. Designer layout, components, and bindings never come down at all.
- Antigravity's agent works the folder. Open the Scratch folder as a workspace and describe the job. Rewrite every excerpt to one sentence, fix the title case, backfill the missing meta descriptions. The agent plans the pass in front of you, then edits file by file. It edits 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 across the whole collection.
- Backfill SEO titles and meta descriptions on the case studies that shipped without them.
- Carry a rebrand through body copy, headings, and SEO fields, watching the pass move.
- Fix title case and formatting drift across collections that grew under different editors.
- Localize a collection into a second language, where Webflow exposes locales.
Watch it work ten items first. Point it at the full collection when the plan and the diffs have earned it.
Why not an MCP server?
A Webflow MCP server wires the agent straight to your live CMS, publish step included. Watching an agent work is comforting right up until a wrong edit lands on the live site anyway, because seeing a mistake is not the same as being able to stop it. Webflow gives you no undo to fall back on.
Scratch separates the two. The agent gets full read and write against a local copy, and the step that touches Webflow waits for you, per item. Antigravity makes the work visible. Scratch makes it stoppable.
What Antigravity 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. The full field list is on Scratch for Webflow.
Questions people ask
Is this an MCP server or a native integration?
Neither. An MCP server bundles the publish step into the agent's connection. With Scratch, the agent edits a local copy, and publishing is a separate step you approve, one item at a time.
Will it touch my Designer layout?
No. The agent 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.
Can I watch the agent before trusting it?
Yes, that is Antigravity's design. The agent lays out its plan in the editor before it works, and every edit lands in a file you can open mid-run. Then the Scratch diff gives you the second look, item by item, before anything ships.
What is Antigravity?
Google's agent-first IDE: an editor built around agents that act on a workspace of files. You sign in with your own Google account. Scratch holds no Antigravity credentials and runs no model.
Do I need to be a developer?
It helps to be comfortable in an editor, but the loop is read and click: read the plan, read the diffs, approve. If an IDE is not your surface, the Claude desktop app runs the same Scratch loop as a plain desktop app.
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.