Brian Gakim

Its been 2 weeks since I launched Dexter, here is how its going so far

Dexter is a plugin i built that runs Claude Code or Codex inside the Framer canvas on the AI subscription you already pay for. Edits don't touch your Framer AI credits.

Since launch I've been emailing everyone who installs it, and the feedback has changed what I'm building.

One user ran 20 prompts in two sessions and told me he'd stopped because he kept hitting his Claude limit on simple edits. I've spent most of the week since then inside model routing and context size, and I've developed opinions about token counts that nobody in my life wants to hear 😁

Others got stuck at setup, so I've made the requirements clearer, you need Claude Code or Codex installed locally first, which wasn't obvious enough before. The framer dev docs are genuinely good, the plugin SDK is a pleasure to work with, and every time I've needed support I've had a real answer within a reasonable time. That's awesome.

If you're already using External Agents, Dexter is the same thing without the terminal: select a layer, describe the change, see the tokens and estimated cost when it lands.

Still early, still rough in places, and I want it to be genuinely useful rather than just interesting. If you try it and something breaks, email me. I'm awake.

What's your experience been with Framer AI credits? Curious whether the burn rate bothers other people as much as it does the designers who've been writing to me.

I spent last week logging every Claude Code run I made in Framer, mostly because I had no idea what any of it was actually costing me.

The big tasks turned out not to be the problem. The vague ones were.

Copy fixes: approximately $0.50 – $5

Section rebuilds: $4–$16

Total: 40+ prompts over ~18 hours, roughly $139 at API-equivalent pricing

My real spend was nothing beyond the $20 Claude subscription I already pay for, which is its own kind of interesting. But the thing that stuck with me was how fast a lazy prompt compounds. I'd ask for something half-formed, get something half-right, correct it, correct it again. Three runs to do one thing.

Being specific the first time is cheaper than being fast.

Disclosure: I built Dexter, which is the only reason I have these numbers at all. It puts Claude Code beside the Framer canvas — select a layer, describe the change, and see the estimated cost when it lands.

If you're running external agents with Framer: do you track your usage, or do you only find out when you hit your limit?

Why pay twice for AI you already use?

If you build in Framer and already pay for Claude or ChatGPT, I built this for you.

Dexter brings Claude Code and Codex directly into the Framer canvas, so you can use the AI subscriptions you already have instead of paying for another set of models.

MCP gives coding agents access to Framer, but the workflow can still feel blind. You often have to manually explain the canvas, the target section, and the context behind every change.

Dexter connects your coding agents directly to the Framer canvas.

Select something or start from scratch and ask Claude Code or Codex to create pages, build sections and components, redesign layouts, improve copy, or refine your site.

Try it out

Introducing Dexter for Framer

Bring Claude Code and OpenAI Codex directly to your Framer canvas.

Create complete pages, sections, and components, redesign existing layouts, improve copy, and make real canvas changes using the AI subscriptions you already pay for.

Dexter also shows your reported token usage and estimated costs, so you can understand how every run spends your AI allowance.

Claude Code and Codex are supported today, with more agents coming soon.

Start with a 7-day free trial: https://dexterplugin.online

I’d love to get feedback and continuously improving it.

Hey everyone,

I’ve been building a Framer plugin that connects Claude Code or Codex directly to Framer, with analytics and controls for monitoring and managing token usage.

I’ve been testing it locally, and it has become an essential part of my workflow. Framer’s SDK and docs have been a pleasure to work with.

Dexter is Coming soon!