All notes

Codex draws in Figma now. The roundtrip is the taste test

OpenAI put Codex inside the Figma canvas this week, and the demo looks fun until you run it on your own files.

I wrote after GA that Figma's guidelines turned taste into a library setting — you write the rules once and the agent follows them on every prompt. The Codex roundtrip is the exam for that setup. Code can become editable Figma designs and Figma files can move back into code, so every weak token and duplicate component now travels in both directions.

The OpenAI-Figma Codex integration creates a code-to-design roundtrip over MCP: Codex turns code UI into editable Figma designs and implements Figma context back into code — and solo founders with tight systems ship faster while messy ones drift twice as fast.

What did OpenAI and Figma actually ship?

A two-way pipe between your repo and your canvas, with your system in the middle.

OpenAI's Codex to Figma announcement describing code-to-design and design-to-code in both directions frames it plainly: bring Figma Design, Make, or FigJam detail into Codex to implement it, then turn UI from code into editable Figma designs to explore ideas before pushing changes back. Start anywhere. Move with context intact.

Transparency first: I haven't wired Codex to my libraries yet — I'm reading the launch notes. What stands out is the plumbing. It runs on MCP, the open standard for agent tool access, through the Figma MCP server inside Codex. Figma's guide to agents working directly on the canvas with components and variables shows what that means: agents edit with real structure — components, variables, auto layout — not flat pixels.

A screenshot importer gives you shapes to trace. This gives you instances to keep.

Why does a roundtrip punish messy systems twice?

Because every flaw now gets two chances to multiply.

Think through one cycle with a loose system. Codex reads your file, guesses which of your three near-identical buttons is canonical, and implements the wrong one. Then it brings that UI back into Figma as fresh layers. You now have a fourth button, born from the earlier confusion.

Most teams will read this as "the agent is sloppy" when the agent did what the files told it to do. A roundtrip doesn't create drift. It copies your drift into a second medium and hands it back.

Tight systems get the opposite math. One button, one card, named spacing — Codex picks right on the way out and generates clean instances on the way back. Each trip confirms the system instead of forking it.

How do you pass the roundtrip taste test?

You shrink what the agent is allowed to touch, then run one small loop.

Here's the prep I'd do before installing anything:

  • One of each. Kill duplicate buttons, cards, and inputs. If two components do the same job, delete one today. The agent can't pick correctly when you never did.
  • Name the tokens. zinc-900 on white, 10px radius beats "dark text, soft corners." Agents match strings, not vibes.
  • Write three rules. One file per repeated correction: which card for browse grids, what never to invent, which spacing scale wins. Keep it under a page.

Then run the test: pick one real screen, send it code-to-canvas and back, and count new variants. Zero means your system held. Anything more is a to-do list, not an agent failure.

When should you stay out of the canvas?

When the job is judgment, not arrangement.

The roundtrip is great at moving decided work between mediums. It won't decide what your empty state should say, which plan to push, or whether that third onboarding step earns its place. Those calls need a person with a point of view and a delete key.

My rule: if the task starts with "which" or "should," keep it with you. If it starts with "turn this into," hand it to the loop. Codex plus Figma moves work fast. You still choose which work deserves moving.

The agent handles translation. You handle taste.

Frequently asked questions

  • A Codex to Figma integration over MCP that works in both directions. Teams can pull Figma Design, Make, or FigJam context into Codex to implement it in code, and turn UI built in code into editable Figma designs for iteration — starting anywhere and moving forward without losing context.

About the author

mosh

mosh is a product designer for growth, working with design thinking and ever-improving design systems. What matters: fixing conversion, whether in B2B dashboards or direct-consumer apps.

Keep reading