Codex Desktop MCP auto connection authorization bug

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

26.513.31313 (2867)

What subscription do you have?

API

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

When I am connecting to MCP servers (in my case Notion and Linear), either:

• I use codex mcp login notion , codex mcp login linear from command line, it opens a browser page with the url it gives asking to trust the 127.0.0.1, i approve, it shows approved in the browser, then I force quit the codex app, and reopen the runtime, it is connected (This one works)
• If I directly tell Codex to look at a ticket in Linear (I had the MCP authenticated before but it does not stays authenticated forever), it launches automatically the webpage for authentication, I click, web page says it is authenticated, but The XXX MCP is configured, but its refresh token is expired/invalid. I’m going to re-authenticate it now; the skill notes a restart may be needed after OAuth, but I’ll see if this live session can pick it up. and then does not continue with this MCP

What steps can reproduce the bug?

1. Go into a session with the coding agent, when Linear/Notion is not yet authenticated/authenticated before but not now;
2. Ask Codex to see Linear ticket xxx, It will pop the authenticate web page, you click authenticate 127.0.0.1, and it will say authenticated, but then Codex will say: The XXX MCP is configured, but its refresh token is expired/invalid. I’m going to re-authenticate it now; the skill notes a restart may be needed after OAuth, but I’ll see if this live session can pick it up.

What is the expected behavior?

After I approve the authentication and the page says authenticated, Codex can access the MCP

Additional information

_No response_