Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Official Figma plugin OAuth stuck after update: 401 Unauthorized / token_revoked [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19801•Fetched 2026-04-28 06:36:54
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
MidoriMAMAMidoriMAMA
Participants
github-actions[bot]github-actions[bot]MidoriMAMAMidoriMAMA
Timeline (top)
labeled ×5commented ×1

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".

Error Message

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

Root Cause

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".

Code Example

figma_whoami

---

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

---

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

---

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

---

http://127.0.0.1:3845/mcp
RAW_BUFFERClick to expand / collapse

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.

extent analysis

TL;DR

The Figma plugin OAuth flow is likely stuck due to an invalidated token, and resetting the OAuth state or re-triggering the authorization flow may resolve the issue.

Guidance

  • Verify that the Figma plugin is properly configured and enabled in the Codex plugin page.
  • Try removing and re-adding the Figma plugin again, and then click "Use in conversation" to see if the OAuth authorization page appears.
  • Check the Codex desktop app settings to see if there are any options to reset or repair the Figma connector OAuth state.
  • If the issue persists, try using the Figma Dev Mode MCP to test the OAuth flow and see if it works as expected.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue seems to be specific to the official Codex Figma plugin OAuth/token state, and the local Figma Dev Mode MCP is working properly. The token_revoked error suggests that the token has been invalidated, and resetting the OAuth state or re-triggering the authorization flow may resolve the issue.

Recommendation

Apply workaround: Try removing and re-adding the Figma plugin, and then click "Use in conversation" to see if the OAuth authorization page appears, as this may re-trigger the authorization flow and resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

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

#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Official Figma plugin OAuth stuck after update: 401 Unauthorized / token_revoked [1 comments, 2 participants]