Letting an AI agent edit your Framer CMS? Here's what Branching protects

What Branching covers

• Changes that have not been merged

  Framer's Branching lesson says a branch inherits pages, components, canvas content, CMS items, collections and styles from its parent, and keeps its own changes on top. Until you merge, CMS edits made on a branch stay on that branch.

• Everything an external agent does

  Framer's External Agents page says every change an external agent makes (Claude Code, Codex, Cursor and others connected over MCP) automatically happens on a branch, and that you can undo changes, review the branch and decide when to merge.

• Prompts to Framer's own Agent from Main

  The Agent creates a branch automatically when you run a prompt from Main. You can also turn on automatic branching to protect Main from direct edits.

Sources: Branching lesson, External Agents, Framer 3.0 announcement.

What it doesn't cover

• Content after you merge

  Merging moves the branch's changes into Main. We could not find Framer documentation for undoing a merge or restoring individual CMS items after one. Once a branch that deleted or overwrote items is merged, treat Main as the only copy unless you saved one first.

• Edits made directly on Main

  If automatic branching is off, your own edits, CSV imports and many plugins write straight into Main, exactly as before Framer 3.0.

• Large changes that are hard to review

  A Changes panel tells you what was edited. It is not a field-by-field diff of 400 blog posts. A rewritten rich-text body or a cleared reference field is easy to miss in a bulk agent run.

• Version history

  Framer's version-history guide describes copying earlier canvas elements into the current project. It does not document restoring CMS items, so it is not a safety net for collection data.

Source: Framer version history. If Framer documents a merge undo for CMS content, we'll update this page.

Checklist before an agent touches your CMS

1. 1

   Save a copy of the CMS before the run: a manual snapshot in a backup tool, or a CSV export of every collection you're touching. Note the item count of each collection.

2. 2

   Tell the agent which collections and fields it may change, and that it must not delete items unless you ask. Ask it to list what it plans to change before it writes anything.

3. 3

   Let the agent work on its own branch, and don't merge anything while it is still running.

4. 4

   Before merging, open the Changes panel and compare item counts per collection with the numbers you noted. Spot-check a few changed items: rich text, images, slugs and references.

5. 5

   If the branch removed or damaged content you need, don't merge it. Fix it on the branch or delete the branch and start again.

6. 6

   Merge, then check Main again before publishing. Merging and publishing are separate steps in Framer, so nothing reaches visitors until someone publishes.

7. 7

   Take another snapshot after the merge, so your next recovery point includes the approved changes.