framer 3.0 and cursor — how i use it across components, templates, and client work
i ship three lanes on framer: marketplace code components, templates, and client sites. 3.0 didn't replace any of them — it finally separated two jobs that used to blur together.
native framer agents stay on the canvas. layout, sections, copy, styles, cms from inside the editor, with visual feedback while it edits. that's still where client design passes and template structure live for me.
external agents — cursor, claude code, codex — connect to the project through framer's agent bridge. cms population, redirects, page updates, migrations from messy files into collections. less export/import, more project-level work from the editor i already use for react and component logic.
my split:
• client sites — canvas for design iterations, cursor for repeatable content edits, seo metadata batches, and redirects across many pages
• templates — scaffold pages and collections faster, then refine breakpoints and components in framer
• code components — react, property controls, scroll math, and motion in cursor; polish and ship in framer's property panel
branching is what makes client work feel safe. external agents batch edits — they don't stream like the in-app agent. i experiment on a branch, review, merge to main. live stays untouched until i publish.
honest limit: external agents are strong for structured project work, not a replacement for designing on the canvas. i still keep both open — framer for visual work, cursor for project depth and code.
setup is one bridge npx @framer/agent setup), then connect your project from cursor.
if you want to try cursor with framer 3.0, my referral's 50% off the first month: