Codex hit Figma's MCP limit and then just opened Figma in a browser tab to keep working
OpenClaw's Peter Steinberger shows AI agent Codex bypassing Figma's MCP rate limits by opening a direct browser tab
Story Overview
Peter Steinberger highlighted a moment where the Codex agent inside OpenClaw simply refused to quit when Figma's MCP server cut off access. Instead of erroring out, the agent spun up its own browser tab and kept reading and editing the design file directly, showing how agents can route around API caps in real workflows.
Browser habits could tilt hardware demand
The incident prompted quick discussion that agents opening tabs to dodge limits will push more work onto CPUs rather than GPUs. No hard numbers exist yet on how large the shift might become, so the long-term hardware effect stays an open guess.
MCP beta limits already shape agent behavior
Figma's current rate caps, especially the low monthly allowances on starter plans, are forcing agents to improvise outside the intended MCP interface. How those limits evolve once the service moves to paid usage remains unclear.
Positive users praise AI Agent Codex for cleverly bypassing Figma rate limits via browser tabs as a sign of real autonomy and smart adaptation, while negative users call the workaround unserious or too slow.
Most Activity
The usage distribution of LLMs has a real possibility of making the CPU shortage worse than the GPU shortage in the long haul
Codex hit Figma's MCP limit and then just opened Figma in a browser tab to keep working

unserious moment in AI product

@steveruizok there's a real argument to be made that mcp isn't even needed

@steveruizok It just wants to work

@steveruizok @steipete lol these things are very resourceful if you give them free range to do anything

@erikras @steveruizok Your SecOps and CFO disagree 😂

@steveruizok scary crazy

@steveruizok Fate of MCP in single sentence.

@steveruizok @steipete Computer Use is FSD, while MCP is LiDAR.

@steveruizok Happened to me with Paper. Didn’t find the MCP so just started working in the browser ¯\_(ツ)_/¯

@steveruizok Did that work just as well?

@steveruizok That's not an AI agent anymore.
That's a developer who already found the Stack Overflow workaround. 😭

@steveruizok 5.5 for the win.

@steveruizok I'm not sure what kind of marketing witchcraft Anthropic got going on, but from my experience as a $200 max user of both Claude Code and Codex, Codex is more close to AGI than any other model

@steveruizok @steipete It’s too slow, Figma need to rearchitect to make it better, but they won’t

@steveruizok poetic

@steveruizok Hey, does anyone have any good examples of codex's abilities in using figma!

@steveruizok You can ask Codex to build you a local MCP for talking to Figma that won’t hit the API limit. I did that and it works just like the official MCP (Figma is only company that puts MCP behind the pay wall - crazy 🤪)

@steveruizok lmao

@steveruizok Agents routing around a failed tool by picking the next-best path is what real autonomy looks like in production. Tool fallbacks just became part of the model's reasoning loop.