With Framer MCP, AI agents can build most of a site. But on real projects with code components, they hit walls that only a person in the editor can get past. Every item below hit us on a live store: Code components are only half writable Fonts: font controls can't be set, and custom fonts aren't available to plugins at all, so every agent-built text falls back to Inter. Grouped properties: Object controls (text styles, box styles, layout groups) are rejected. New properties after a library release: reported as "Unknown control" by the agent, while the editor shows them. Instance updates: library instances can only be updated by clicking Update in the editor, one by one. Slots: slot values can't be read through the plugin, aren't passed to hidden(), and inserting an instance into some components fails. Editor data: CMS link lists arrive empty on the canvas and in Preview, and components with an auto layout get no width. Branching and publishing aren't safe for agents One shared branch: all agent sessions on a project share one active branch, so two agents switch each other's work. Creating branches: branches can't be created on demand, and switching then editing can land on the wrong branch. Publish preview: on main, it publishes production. Publish diff: it lists component names, not what changed, so an agent can't judge whether a change is safe to ship. Agents can't see the result Preview: no access to the editor's Preview or its console. Library versions: no way to see which version an instance is on versus the latest. Compile errors: a code file that fails to compile gives no clear error back. Ask: what the editor can do, the Plugin API and MCP should be able to do too. That means writable fonts (custom included) and grouped controls, a programmatic instance update, branches per session, a publish preview that doesn't deploy, a readable diff, and access to Preview and its errors. Agents can already build the structure of a site. With these, they could finish and ship it without anyone fixing it by hand.
