Plugin Linear authentication token expired in threads

What issue are you seeing?

Summary:
After the Linear connector token expired in one Codex thread, reconnecting/signing in again did not restore Linear access in that same thread. The Linear plugin continues to return token_expired there, while Linear works normally in other Codex threads under the same account/session.

Expected behavior:
Reconnecting the Linear app in Codex should refresh the auth state for all relevant threads, or at minimum for the current thread after reconnect. After re-authentication, Linear MCP calls in the thread should start working again without needing a new thread.

Actual behavior:
In this thread, all Linear plugin calls continue to fail after reconnect with:
Provided authentication token is expired. Please try signing in again.

At the same time, the Linear plugin works in other Codex chats.

Why this looks like a Codex bug, not a Linear bug:

The same Linear account works in other Codex threads.
Re-authentication succeeds from the user side, but this thread keeps using stale auth.
The failure happens during the MCP handshake for this thread, which suggests stale thread/session connector state or auth cache invalidation not propagating correctly.
Repro steps:

Use the Linear plugin in a Codex thread.
Let the Linear auth token expire, or reach a state where the thread starts returning auth errors.
Reconnect/sign in again to Linear from Codex.
Return to the same thread and try a Linear action again.
Observe that the thread still fails with token_expired.
Open another Codex thread and use Linear there.
Observe that Linear works in the new thread.
Observed error:
Provided authentication token is expired. Please try signing in again.

Impact:

Existing thread becomes unable to use Linear even after user reconnects.
Work is interrupted because project tracking actions must be moved to another thread or done manually.
Creates confusion about whether the failure is in Linear, Codex, or the user’s auth state.
Workaround:

Start a new Codex thread where Linear may work again.
Or update Linear manually outside this thread.
Restarting Codex may also help, but reconnect alone did not fix this thread.
What Codex should investigate:

Thread-local connector auth caching
MCP session reuse after connector re-authentication
Whether reconnect events invalidate stale auth in already-open threads
Whether plugin/session state is pinned to the thread and not refreshed after reconnect

What steps can reproduce the bug?

Create a thread

What is the expected behavior?

_No response_

Additional information

_No response_