Desktop-only tools disappear after switching to mobile and do not recover in the same thread

Summary

In a thread where desktop-only integrations were initially available and working from the Codex desktop app, opening or continuing the same thread from the mobile app caused those tools to disappear. After returning to the desktop app, the same thread did not regain access to those tools.

Affected integrations observed in practice:

• Figma plugin / Figma MCP tools
• Atlassian plugin / Jira MCP tools

Expected behavior

When returning to the desktop app, the thread should either:

• restore desktop-only integrations on the next turn, or
• reinitialize the tool/plugin/MCP context for that thread.

At minimum, desktop should not remain stuck with the reduced mobile tool context.

Actual behavior

After switching to mobile:

• Figma tools stopped being callable
• writable Jira/Atlassian tools stopped being callable
• tool search could still suggest that related integrations/capabilities existed somewhere in the system, but they did not materialize as callable tools in the thread
• returning to desktop did not recover those tools in the same thread

Later, some tools came back asymmetrically:

• GitHub tools reappeared
• Jira/Atlassian tools reappeared
• Figma tools still did not reappear

This makes it look like the thread capability context is being partially overwritten or only partially rehydrated after mobile participation.

Impact

• Live Figma audits became impossible in the affected thread
• Jira/WMT updates could no longer be performed reliably from the affected thread
• Work had to continue using repo artifacts only, without live external integrations
• Long-running mixed desktop/mobile workflows become fragile

Reproduction steps

1. Open a thread in Codex desktop.
2. Use a desktop-only integration successfully, for example Figma tools.
3. Open or continue the same thread from the mobile app.
4. Return to the same thread in the desktop app.
5. Try to use the same Figma/Jira tools again.

Result

The tools are no longer available in that thread, or they reappear only partially/inconsistently.

Notes

This looks like one of the following:

• thread-level capability context corruption after mobile handoff
• failure to rehydrate desktop-only plugin/MCP bindings on desktop return
• mismatch between tool discovery and active callable tool attachment
• mobile turns overwriting the thread's active integration context

Useful investigation areas

• Thread capability context after mobile handoff
• Rehydration of desktop-only plugin/MCP bindings on desktop return
• Difference between tool_search discovery and active callable tool attachment
• Whether mobile turns overwrite the thread's active integration context