pi is the coding agent you configure to fit your workflow exactly. Where most agents are generic tools you adapt yourself to, pi is the one you shape to yourself: your content, your voice, your validators, your rules. Point it at a codebase and it edits like a developer who already knows how you work. The same is true for your Webflow CMS, with one catch. The CMS is not a folder pi can open, and the live site has no undo if it gets a rewrite wrong.
Scratch makes your collections that folder. pi does 99% of the work, reading every item and rewriting it on your laptop according to the configuration you have built for your site. The last 1%, what actually publishes, stays a button only you press. Nothing reaches the live site until you have seen the change as a diff and approved it. And because pi is yours, the prompts, validators, and voice guidelines you wire in today run on the next collection too, without rewriting instructions from scratch.
How it works
- Scratch pulls your collections into files. Every CMS item, page, and asset comes down to a folder on your laptop, one file per item. The Designer layout never moves.
- pi edits the items. Point pi at the Scratch folder and give it the instruction. It works the collection the way it works a repo, reading each file and writing the change you asked for. Rewrite every excerpt to one sentence in the voice we use for case studies. Fix title case. pi touches the files, never the live site. Validators you have configured catch anything that steps outside your rules before you even see the diff.
- You review every diff and publish. Scratch shows each change next to 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 never leaves your laptop.
What people use it for
The jobs that pile up because the Webflow editor opens one item at a time:
- Tighten every blog excerpt to a single sentence in the voice your team uses, not a generic summary.
- Backfill SEO titles and meta descriptions on collections that shipped without them, each within Webflow's character limits.
- Carry a rebrand through a whole collection: body copy, headings, and SEO fields in one pass.
- Write alt text across an image-heavy case-study set.
- Localize a collection into a second language, where Webflow exposes locales.
Run it on a handful of items to settle the configuration, then point it at the whole collection.
Why not an MCP server?
A Webflow MCP server wires an agent straight to your live CMS, publish button and all. One confident pass ships across the whole collection, and Webflow gives you nothing to roll it back with. For a site built on content you have spent time getting right, that is too much trust to hand over without a review step.
Scratch gives pi the same full read and write access, but against a local copy. The publish step is lifted out and handed to you. pi can change anything; only you can ship it. On a live site with no undo, that gap is the whole point. And because pi stores configuration, you set up the guardrails once and they travel with every job after that.
What pi 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
The Designer layout, components, bindings, and reference targets are never exposed for editing. Validators check length caps, slug uniqueness, and any field you mark off-limits, so a rewrite cannot overrun an SEO limit or quietly break a binding. Because pi is configurable, you can add your own rules on top of those defaults: tone checks, terminology lists, field-level constraints specific to your site. Ecommerce collections are out of scope. The full field list lives on Scratch for Webflow.
Questions people ask
Is pi a general-purpose coding agent or is it built for content work?
pi is an open-source CLI coding agent built to be configured. It handles code, content, and anything else that lives in files. On Webflow CMS collections through Scratch, it edits content fields the same way it edits source files: one instruction, every item, result as a diff. The difference is that you can configure pi with your voice, your validators, and your terminology so the output already fits your site before you read the first diff.
Will it touch my Designer layout?
No. pi only sees the content fields Scratch pulls. Layout, components, bindings, and reference targets are never pulled into the folder, and validators stop a rewrite from breaking a slug or blowing a length cap.
Webflow has no undo. Am I stuck if a rewrite is wrong?
No. Scratch keeps the original beside the rewrite, so every published item rolls back per row, even though Webflow itself cannot. You decide which version stays.
How is this different from a CSV round-trip or a script?
A CSV re-import and a hand-written script both write straight to the live CMS with no diff and no per-item approval, and a find-and-replace does only what you spelled out. pi brings judgment to the messy cases a rule cannot handle, and Scratch still holds every change for review before anything ships. Add your own validators to pi and the judgment is shaped by rules you wrote.
Can it sweep a whole collection from one prompt?
Yes. That is the use case. Run it on a few items first to settle the prompt and confirm the output fits your voice, then point it at the whole collection.
See it on your own collection
The fastest way to trust it is to watch it run on your content. See it run on your Webflow CMS →, or download Scratch free and run the first pass yourself.