Official Figma plugin OAuth stuck after update: 401 Unauthorized / token_revoked

Summary

After a recent Codex desktop update, the official Figma plugin OAuth flow appears stuck. The Figma plugin is enabled and available in conversation, but official plugin calls fail with 401 Unauthorized. No Figma OAuth authorization page appears when removing/re-adding the plugin or clicking "Use in conversation".

Environment

• Codex desktop app: 26.422.30944
• Bundle version: 2080
• OS: macOS
• Plugin: Figma (openai-curated)
• Date observed: 2026-04-27

What I tried

• Removed and re-added the Figma plugin
• Revoked Figma connected app access
• Restarted Codex
• Logged out of Codex and logged back in
• Clicked "Use in conversation"
• Confirmed the plugin is enabled in the Codex plugin page

Expected behavior

After revoking/removing/re-adding the plugin, Codex should launch the Figma OAuth authorization page and save a fresh token.

Actual behavior

No Figma OAuth page appears.

Official plugin call:

figma_whoami

Current error:

Error code: UNAUTHORIZED
Error: McpServerError: Your MCP server returned HTTP 401: Unauthorized

Earlier error after revoking the token:

Encountered invalidated oauth token for user, failing request
code: token_revoked
status: 401

There was also one transient plugin startup error:

MCP startup failed: timed out handshaking with MCP server after 30s

Additional signal

Local Figma Dev Mode MCP is healthy and responds at:

http://127.0.0.1:3845/mcp

I verified that local MCP can initialize and list Figma Dev Mode MCP tools such as get_design_context, get_screenshot, and get_metadata. This suggests Figma Desktop/local MCP is working, and the failure is specific to the official Codex Figma plugin OAuth/token state.

Request

Please reset or repair the Figma connector OAuth state for my Codex account, or provide a way for the desktop app to force re-trigger the Figma OAuth authorization flow.