Existing desktop threads do not pick up newly enabled MCP connections

What version of Codex is running?

Codex desktop app on macOS

What issue are you seeing?

When I enable a new MCP connection in the Codex desktop app (for example Notion MCP), the newly enabled MCP does not become available in the current thread.

The only reliable workaround is to start a new thread or restart the app.

Steps to reproduce

1. Start a Codex desktop thread.
2. Work in that thread normally.
3. Enable/authenticate a new MCP connection in the app, such as Notion MCP.
4. Return to the existing thread and try to use the newly enabled MCP-backed tools.
5. Observe that the current thread still does not have the new MCP tool availability.
6. Start a new thread or restart the app.
7. Observe that the MCP connection may now become available there.

Expected behavior

If a new MCP connection is enabled successfully at the app/account level, the current thread should either:

• automatically pick up the new MCP tools, or
• provide an explicit refresh/rebind action

Actual behavior

The current thread keeps running with the old tool set and does not gain access to the newly enabled MCP connection.

Why this is a problem

This makes MCP connection changes effectively thread-scoped in practice, even though they are configured at the app level.

It also forces users to abandon the current thread if they need to use the newly enabled MCP.

Additional context

This was reproduced with Notion MCP.

The issue seems less like a Notion configuration problem and more like app-level MCP auth/connection state and thread-level tool availability getting out of sync.