Figma plugin reads time out after 120s

Open 💬 1 comment Opened Apr 3, 2026 by moxw

What version of the Codex App are you using (From “About Codex” dialog)?

26.325.31654 • Dev

What subscription do you have?

Pro

What platform is your computer?

Linux 6.19.6-arch1-1 x86_64 unknown

What issue are you seeing?

When using the Figma plugin in the Codex App, authentication succeeds and whoami works, but Figma read operations hang until the 120 second tool timeout or occasionally fail with an upstream transport reset.

This blocks Figma-driven UI implementation even though the plugin is visibly connected and the same session can read the authenticated Figma identity.

What steps can reproduce the bug?

  1. Connect the Figma plugin in Codex App and confirm authentication works.
  2. Use the Figma plugin read tools against one or more design files or nodes.
  3. Call get_metadata, get_screenshot, or get_design_context.
  4. Retry serially, one call at a time.
  5. Observe that whoami still works, but file reads stall until timeout.

What is the expected behavior?

Figma read tools should either return metadata, context, or screenshot successfully, or fail quickly with a clear file-level error. They should not consistently consume the full 120 second tool timeout when authentication is already valid.

Additional information

Observed errors:

  • timed out awaiting tools/call after 120s
  • Unexpected content type: text/plain; body: upstream connect error or disconnect/reset before headers. reset reason: connection termination

Notes:

  • whoami succeeded in the same session and returned the authenticated Figma user
  • the problem reproduced with both page-level and node-level requests
  • retrying serially instead of in parallel did not fix it
  • this worked intermittently earlier, so the failure appears flaky rather than a permanent auth misconfiguration

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗