On June 2, OpenAI shipped six new plugins for Codex, its coding agent, and asked users to think of them the way they’d think of a browser extension: install, point at a task, get an output. The six roles on offer — Data Analytics, Creative Production, Sales, Product Design, Public Equity Investing, and Investment Banking — sit in the same menu, drawing on the same underlying architecture of “62 apps and 110 skills,” according to IT Brief. The framing, in OpenAI’s own words as reported by TechCrunch, is that “each of the new tools bundles integrations, instructions, and context to allow Codex to approximate a specific job.” That single verb — approximate — is doing more work than it looks like, and product design is the plugin where the gap between approximation and the real thing is widest.
The Product Design plugin, per Reworked, “turns early ideas into prototypes teams can review, with work that can be carried forward in tools like Figma and Canva.” Concretely, IT Brief reports it supports user-flow reviews, prototyping from a live URL, and turning static screenshots into interactive designs. Feed it a prompt or a screenshot, and by the end of the same session you have something that looks like a deliverable: a clickable flow, a set of Figma-ready screens, a review of how a user might move through an existing product. For a non-designer — a founder, a PM, an engineer who needs a mockup to unblock a conversation — that is a genuinely useful shortcut, and it’s easy to see why OpenAI is chasing exactly that audience: knowledge workers now make up about 20 percent of Codex’s more than 5 million weekly active users and are growing more than three times as fast as developers, according to TechCrunch.
What a same-day output leaves out
The trouble is that product design, as a discipline, is not mainly a generator of artifacts. Prototypes and Figma files are the residue of a process, not the process itself, and the part that gives those artifacts their value is precisely the part a plugin can’t bundle: the crit where three people disagree about whether a flow actually reduces friction or just moves it, the round of usability testing that reveals the “obvious” solution confuses half the users who try it, the negotiation with a stakeholder who wants a feature that contradicts the research. That back-and-forth is contested by design — it’s supposed to surface disagreement early, when it’s cheap to resolve, rather than late, when it’s baked into a build. Compress it into a single install that produces a finished-looking screen in one pass, and you don’t eliminate that contestation; you just relocate it to after the fact, once something already looks done enough that questioning it feels like friction rather than diligence.
It's the part of product design that was already easiest to fake.
The tell is in the taxonomy
What makes the framing more telling than the feature itself is the company it keeps. OpenAI lists Product Design next to Investment Banking and Public Equity Investing as equivalently packageable jobs — bundles of integrations and instructions, interchangeable in structure if not in content. Nothing in the public description acknowledges that design judgment is a different kind of expertise than modeling a discounted cash flow, because a mockup can look complete without ever having been tested against a real user, in a way a spreadsheet generally cannot fake. Treating “product design” as a slot in a six-item role menu is a small taxonomic choice with a large implication: it says the discipline’s specificity — the part that resists being reduced to inputs and outputs — isn’t something the product needs to model.
There’s a useful mirror here to Figma’s own recent move of pulling code layers into its canvas, folding development into a design tool’s surface. Codex’s Product Design plugin runs the same trade in the other direction: a coding agent absorbing design, treating prototyping as an output a well-instructed model can generate on demand. Figma’s own earlier integration with Codex, described on the Figma blog, was pitched explicitly around collaboration between disciplines — “when code and the canvas are connected, you can move fluidly between execution and exploration” — which at least kept a human designer moving between two states. The plugin version drops that framing; it’s not built for someone who already does the moving. It’s built for someone who’d rather skip the movement and get the destination.
None of this means the plugin is useless — a fast, disposable prototype for internal alignment is a real thing worth having. But it does mean the industry should be precise about what’s being automated. It isn’t product design. It’s the part of product design that was already easiest to fake.
