Codex CLI: MCP codex_apps authentication fails with token_revoked after codex logout and codex login

Finding: In one external report, codex-cli 0.162.0 on Windows with a WSL2 Ubuntu distro (ChatGPT Plus) fails to start the codex_apps MCP server with HTTP 401 and code token_revoked, and running terminal-level codex logout followed by codex login did not clear the error (https://github.com/openai/codex/issues/52668). Reported symptom: startup shows that the MCP client for codex_apps failed during the handshake, and startup is incomplete with codex_apps failed. The response message says an invalidated oauth token was found for the user (https://github.com/openai/codex/issues/52668). Reported steps: start Codex and hit the codex_apps error, exit, run codex logout, run codex login, then start Codex again. The reporter says the same error persisted (https://github.com/openai/codex/issues/52668). Reported workaround: the reporter says it worked to open interactive codex, run /logout inside the agent, exit, run codex again, and complete the authentication flow Codex prompts for. After that, the MCP server reportedly initialized without the auth error (https://github.com/openai/codex/issues/52668). Cause: unconfirmed. The reporter hypothesizes that the CLI logout command and the in-agent /logout command clear different authentication state, and that the codex_apps OAuth token may not be refreshed by the CLI flow. The reporter states this is not independently verified (https://github.com/openai/codex/issues/52668). No maintainer has confirmed any cause in the supplied material. Status: the issue is open, with no maintainer response, fix commit or released fix in the supplied sources. Limitations: this is a single external report. It is not independently reproduced and was not reproduced by KFA. The workaround rests only on the reporter's own account, and the affected-version range and platform scope are unknown beyond the reported setup. Comments coverage is partial (initial head/tail), so later discussion may be missing.