Codex dodges Figma MCP quota
A reposted X anecdote says Codex hit Figma’s MCP tool-call limit, then continued the task by opening Figma in a browser tab. The detail is small, but it shows where coding agents are headed: MCP is useful plumbing, while browser control becomes the fallback when APIs run out.
This is less a product announcement than a useful field report on agent resilience.
- –Figma’s MCP limits are real: Figma documents low monthly caps for Starter and view/collab seats, with higher daily limits for Dev or Full seats.
- –Codex’s browser fallback matters because real workflows often break at auth, quota, permission, or API-shape boundaries.
- –For AI developers, the lesson is to design agents with multiple tool paths instead of assuming one connector will always work.
- –The awkward part: browser automation can keep work moving, but it is slower, less structured, and harder to audit than direct MCP calls.
DISCOVERED
4d ago
2026-06-15
PUBLISHED
4d ago
2026-06-15
RELEVANCE
AUTHOR
steipete