Yes, through Framer's own AI agents or through Framer's official External Agents connection for Claude Code, Codex and Cursor. A normal ChatGPT or Claude chat is not connected to your project, so it can only draft text and code for you to paste in. Framer's in-editor agent generates pages, CMS content and code components from a prompt. Its External Agents bridge needs no third-party MCP server and lets an outside coding agent change supported parts of a real project through Framer's own API. Framer has no code export, so every route stays on Framer's platform.
What does Framer's own AI do today?
Framer's in-canvas AI agent can "create editable pages, sections, copy, and visuals directly in your project" from a written description. You can keep refining in conversation or take over on the canvas at any point (Framer, AI website builder). The same page describes four connected jobs: generating a page or section layout, building a custom code component from a description, reviewing a site for "contrast issues, typos, missing alt text, SEO gaps, and inconsistent styles," and turning site analytics into "practical next steps."
Two of these skills have their own names and launch dates. Wireframer generates a purpose-built page layout ("clear, purpose-built layouts that focus on structure, not style") that you then finish on the canvas. Framer announced it on May 21, 2025 (Framer Updates, "Wireframer"). Workshop turns a description into a React code component with property controls already wired up, announced the same day (Framer Updates, "Workshop").
These AI features run on credits, not a flat "AI included" switch. Framer's pricing page lists the monthly agent credits for each plan (Framer, Pricing). Check it for your plan, since credit allowances change.
Can outside AI edit my existing Framer site?
Yes, through Framer's official External Agents connection, which is a documented feature and not a workaround. Framer's pricing page lists "External agents" as a line item under Agents, marked PREVIEW, described as "Connect your own tools with Framer" (Framer, Pricing).
To set it up, run npx @framer/agent setup in a terminal, which installs a Framer skill into your agent's own skills folder. Framer's help center states plainly, "Framer doesn't require a separate MCP server. If you're searching for a Framer MCP, the native Framer Agent connection gives Claude Code, Cursor, Codex in ChatGPT, Gemini CLI, and other AI tools direct access to your canvas, components, CMS, and project context, without manual MCP setup" (Framer Help, "Use external agents with Framer", updated August 7, 2026). You then open the agent, give it your project's link, and approve the connection the first time it is requested: "The first time you use an external agent with a project, Framer will open your browser and ask you to allow the connection to your project" (same source).
This route suits structured, repeatable, data-driven work rather than open-ended visual design: importing a CSV into the CMS, syncing localized strings from a translation file, writing a React code component, or auditing a site for missing SEO fields, each with a worked example prompt (Framer Help, "What you can do with Claude Code, Codex in ChatGPT, and other External Agents", updated August 7, 2026). Framer's own FAQ answers the direct question: "Can Claude Code or Codex in ChatGPT change my project? Yes. After authorization, Claude Code, Codex in ChatGPT, or another supported external agent can help create and update supported Framer content and project resources. Review changes before publishing" (same source).
| Route | What it reaches | What it needs |
|---|---|---|
| Framer AI agent (in-canvas) | New pages, sections, code components, site review, analytics summaries | A Framer account, agent credits |
| External Agents (Claude Code, Codex in ChatGPT, Cursor, and other tools) | CMS content, localization, redirects, pages/sections, code components | npx @framer/agent setup, Node.js 24+, one-time browser authorization |
| Framer code components (manual) | Custom React components on the canvas | React 18-compatible code, written in Framer's built-in editor |
What can't a connected agent touch?
Framer's setup guide for local LLM agents lists this under "Known limitations." As of the same August 7, 2026 update, External Agents "aren't currently supported" for:
- Deleting, renaming, or moving pages
- Updating site settings or project settings
- Assigning code overrides to nodes
- Accessing analytics data
(Framer Help, "How to set up Framer for Claude Code, Codex in ChatGPT, and Cursor")
Framer's FAQ adds the general rule: an external agent works through "Framer's API," on "supported Framer content and project resources," which is not a blank grant to change anything an owner could change in the editor. Treat any capability the help pages do not list as out of scope until Framer documents it.
Is there a developer route into a Framer site?
Yes: code components, written by a developer inside Framer itself. A Code Component is "a React Component that can extend Framer's capabilities by rendering directly on the canvas, in the preview, and on your published site," built in Framer's own code editor with a live preview, and it must use React 18-compatible code (Framer Developers, "Introduction"). Property Controls expose the component's props as visual controls in Framer's panel, so a non-developer can still configure it once it exists. This is the route for custom, code-level features such as a pricing calculator, a live map or an API-driven widget.
It is not a way to pull your Framer site's source out to run somewhere else. Framer's help center is direct about that: "Framer does not offer HTML export for self-hosting," because published sites depend on Framer's backend services and "cannot be exported as standalone HTML files for self-hosting" (Framer Help, "Can I export my website to HTML and self-host it?", updated August 7, 2026). Our export capability matrix covers this alongside 15 other builders. Framer is one of the ones with no code-export path today.
How do I set up an outside agent safely?
- Name the one job. "Sync these CMS items from a CSV" is a clean External Agents task. "Redesign the homepage" is a canvas job for Framer's own AI agent or you.
- Install the agent connection once. Run
npx @framer/agent setup, then connect from your terminal-based agent. Framer's setup guide names Claude Code, Codex in ChatGPT and Cursor. - Approve the browser authorization. This happens once per project. Do not reuse an old approval for a project you did not intend to grant.
- Ask for a plan before changes. Framer's recommended workflow is to ask the agent to inspect, propose a plan, review it, then let it apply changes and summarize what changed.
- Review before publishing. Both Framer's in-canvas AI and its External Agents leave publishing as a separate, reviewable step. Use it.
- Never give ChatGPT or Claude your Framer password, a security code or a browser session. The connection above uses Framer's own browser approval and needs none of them.
When does leaving Framer make sense?
Not to get AI involved, because Framer's own agent and External Agents already reach a real slice of a site's content, code components and structure. Consider a different platform when you want your design's source of truth to be the Figma file itself rather than a project that lives natively in Framer, or when the per-editor, per-credit pricing outweighs what a simpler, design-driven site needs. If your site started in Figma, the comparison of what that move costs you is in Framer vs Figment: which should publish your Figma design?.