Framer 3.0 - With Agents, Branching, Community, and an all-new design
by•
Agents bring AI to the canvas to help you design, write, analyze, and organize your sites. We’re also launching Branching, a new way for teams to explore ideas before they go live, and unveiling the new Framer Community, where creators can share and earn. Together, these launches change how teams create, maintain, and scale websites. We think you’ll love it.


p/reso
p/runevr
p/dex-by-exmergo
p/producthunt
p/google-cloud-platform
p/ai-context-flow
p/kodlo
p/seshka
p/duckfightclub
p/talanoa-2
p/nudgeforme
p/nexupira
p/many-displays
p/murror
p/operum
p/dino-kids
p/tabstack
p/rithub
Replies
Really like the direction here — publishing straight from AI-generated design closes a gap a lot of tools leave open. One thing I'd be curious about: as AI-generated content (design or video) becomes the norm, are you thinking at all about provenance/attribution for what's AI-made vs. human-edited? It's something we've had to build for from day one on the video side, and I imagine it'll matter increasingly for design too.
Branching is the part that interests me most. When an agent explores a variation in a branch, can you merge just part of that branch back into the main site, or is it all-or-nothing? And does a branch keep CMS content and interactions intact while you're experimenting?
Really like that Agents can connect to external AI tools like Claude Code rather than being locked into one black-box assistant. How do you handle it when an agent's suggestion conflicts with an existing design system or component constraints — does it flag the conflict or override it?