Figma connector in Codex desktop is read-only; use_figma write tool missing

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

26.609.41114

What subscription do you have?

Enterprise

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

The Figma connector in Codex desktop is exposing only read-oriented tools and does not expose the expected write-capable use_figma tool.
Current Figma tools available in the session:
_get_metadata
_get_design_context
_get_screenshot
_generate_diagram
_generate_deck
Missing capability:
No mcp__codex_apps__figma._use_figma
No use_figma
No equivalent tool that can execute Figma Plugin API write operations on editable Figma design files
Impact:
Codex can inspect Figma files but cannot create or edit canvas layers
This blocks workflows that require creating frames, text layers, shapes, Auto Layout, components, variants, or variables from Codex

What steps can reproduce the bug?

1. Open Codex desktop with the Figma connector installed.
2. Ask Codex to inspect the available Figma MCP tools.
3. Verify the exposed tools under mcp__codex_apps__figma.
4. Look specifically for a write-capable tool such as:

• mcp__codex_apps__figma._use_figma
• use_figma
• any tool that can execute Figma Plugin API code

1. Observe that only these tools are exposed:

• _get_metadata
• _get_design_context
• _get_screenshot
• _generate_diagram
• _generate_deck

1. Reconnect the Figma plugin.
2. Restart the Codex desktop app fully.
3. Repeat the same tool inspection.
4. Observe that the write-capable tool is still absent after reconnect and restart.

What is the expected behavior?

The Figma connector should expose a write-capable tool such as use_figma for editable Figma design-canvas operations.
Expected capabilities include:

• creating frames
• creating text layers
• creating rectangles/vectors
• applying styles
• setting Auto Layout
• creating or updating components
• creating or updating variables and variants

A minimal smoke test should be possible, for example:

• create a temporary frame named Codex MCP Write Test
• add a text layer inside it
• return created node IDs or success metadata

Additional information

Evidence that use_figma is expected in this environment:

• Local attachment/skill text explicitly documents use_figma as the MCP path for executing Figma Plugin API code: [pasted-text.txt (line 1)](/Users/jgarrick/.codex/attachments/6afe885e-fcd8-457e-9b00-6dbf4a1511d3/pasted-text.txt:1)
• Bundled Figma skill docs in the Codex install also explicitly reference use_figma: [SKILL.md (line 1)](/Users/jgarrick/.codex/plugins/cache/openai-curated-remote/figma/2.0.9/skills/figma-use/SKILL.md:1)

Evidence from local Codex caches:

• Cached Figma tool registry contains only 5 Figma tools and no use_figma: [ffe70939e7bdcac3e104129cb4e838f9428d550d.json (line 1)](/Users/jgarrick/.codex/cache/codex_apps_tools/ffe70939e7bdcac3e104129cb4e838f9428d550d.json:1)
• Local app directory marks the Figma connector as isEnabled: true but isAccessible: false: [ebdcfad6684efa0a44e0113d153a29a7edf79a0d.json (line 18224)](/Users/jgarrick/.codex/cache/codex_app_directory/ebdcfad6684efa0a44e0113d153a29a7edf79a0d.json:18224)

Why this appears to be a connector/platform issue rather than a file-permission issue:

• If this were only a Figma file ACL problem, I would expect a write tool to exist and then fail during execution
• In this case, the write tool itself is absent from the exposed tool surface

Environment:

• Codex desktop app
• macOS
• Figma connector reconnected
• Codex app fully restarted
• Issue persists after restart