Framer's agent now edits your styles, not just the page.

With Harness 2, Framer's agent can change component properties and styles across a whole project. For design, what it can edit matters more than how fast it runs.

By @ignapradosNews3 min read

On November 2, Framer published Harness 2, a rebuild of the engine behind its agent. Speed makes the headlines. What matters for anyone looking after design is something else: the list of what the agent can now touch.

Here's what Framer says in its announcement, what it leaves out and how I'd use it.

What Framer announced

Framer says it rebuilt the agent's harness to take on whole workflows in a single program. Per the announcement, it now reads the document, decides and applies changes while the model is still writing the next steps, using 2x fewer tool steps and 39% fewer cached input tokens per message. Those are the company's own figures, and the page doesn't say how they were measured.

The capabilities, as Framer lists them:

  • Components: object and array fields, more types and animation settings.
  • Styles: more properties across the project's styles.
  • CMS: sorting by multiple fields, status and creation date.
  • Code and SVG: read and edit code, and add or update SVGs.
  • Branches: create, switch, rename, join and delete.
  • Forms: custom email recipients and webhook destinations.
  • Access: content editors can edit and undo CMS changes; viewers can ask but can't edit.

Framer adds that the same capabilities reach external agents through MCP.

Why styles and branches matter more than speed

An agent that only generates new pages tends to repeat what it has seen most. One that can modify project styles and component properties works on decisions you already made: change a radius or a color in the style, not in forty loose blocks. It's the difference between editing a system and redrawing a page.

Branches make trying things cheap. If the agent rewrites a style, you can look at it on a branch and discard it. That's my inference from the list, not something Framer promises: the announcement doesn't say how the agent applies your design system or how well it respects your choices.

It points the same way as Figma's model for editing existing designs: less generating from scratch, more modifying what's there.

The agent in Convert, the other release

A day later, on November 3, Framer added agent support to Convert, its testing tool: you can ask it to create, edit and analyze funnels and A/B tests, or add and edit triggers. Country-based triggers arrived too, for example showing visitors in Spain a banner for an event in Barcelona.

There's a clear design risk. If the agent makes launching variants easy, you'll get more A/B tests of headlines and buttons and fewer decisions about page hierarchy. A test compares two options; it won't tell you both are generic.

How I'd use it this week

First, define the styles by hand: the type scale, the radii and the colors. Then ask the agent to apply them, not invent them. An instruction like this sets the limit:

Use only the text and color styles that already exist in the project. Don't create new styles or change values without telling me. If you need something that isn't there, tell me which and why. Work on a branch.

And measure the result: the Slop Score flags signals like repeated typography or identical rounded corners everywhere, exactly what a loose agent leaves behind. If one shows up, the guide to fixing it has the next step.

Sources

Frequently asked questions

What is Framer's Harness 2?

It's the rebuilt engine behind Framer's agent, announced November 2, 2026. It runs whole workflows and can edit components, styles, CMS, code and branches.

Can Framer's agent change my project styles?

Per Framer, it can add and customize more properties across the project's styles. The announcement doesn't detail how it respects your design system.