Framer 3.0 - With Agents, Branching, Community, and an all-new design

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.

Add a comment

Replies

Best

congrats on the launch. branching is the feature i didn't know i needed until now. letting teams explore without touching prod is the kind of thing that quietly unblocks a lot of back-and-forth. excited to see where the agent stuff goes inside the canvas.

The Branching feature is a game-changer. We're a small nonprofit team building our donor-facing platform and being able to try different page layouts without risking the live site is exactly what scrappy teams need. Congrats on the launch.

Big congrats! Framer keeps raising the bar. Love how it makes design + dev feel effortless. Excited to see where the team takes it next!

Congrats on the launch! How do you plan to handle feedback with the activity rise these days?

As someone who designs in Framer regularly, the AI has been incredible. The screenshot understanding is genuinely useful, and I was surprised by how well it creates components and maintains structure instead of generating one-off layouts.

I'm curious moving forward: do you see the AI evolving into more of an agent that can analyze an entire website, understand the existing design system and brand guidelines, and then generate new pages and components that are fully consistent with that system?

Congrats on the launch. The part I like most is that the agent works directly on the canvas while still leaving the changes visible and editable.

As a solo founder, that matters a lot. I want help moving faster on landing page ideas, but I still want to understand and control what changed before publishing.

The agent/workflow angle in Framer AI Agents is interesting. One thing I’d love to understand is how you handle handoff when the automation is not confident — do users get a clear review step before changes go live?

The Claude Code / Codex connection is the part I’d want to test first. One question: when an agent changes a live-ish site, does Branching keep the AI edits easy to review as a clean diff, or is it more like comparing page states visually?

Branching for design files is the unsung hero here, didn’t know I needed it until now.

Easy to use, easily customisable. Clients love it.