Last version doesn's work on VS code for Linux

Open 💬 4 comments Opened Jun 29, 2026 by Marine-DR

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.623.61823

What subscription do you have?

Plus

What platform is your computer?

Bazzite Linux 7.0.9-ogc3.2.fc44.x86_64 x86_64 unknown

What issue are you seeing?

Title: Latest Codex VS Code extension regression on Bazzite (Fedora): authentication UI disappears

Environment

OS: Bazzite (Fedora-based Linux)
VS Code: (add your version)
Previous extension version: working
Latest extension: broken
Downgraded manually to 26.623.41415, which works correctly.

Issue
After updating to the latest version of the Codex VS Code extension, the authentication UI disappeared completely. There was no Sign in button or any way to authenticate.

Expected behavior
The extension should preserve the existing session or display a Sign in button if authentication is required.

Actual behavior
With Codex v26.623.61823, the extension panel shows only a fixed/static ChatGPT icon. There is no Sign in button, no authentication UI, and no visible error message.

Logs
No errors appeared in Output → Codex or Developer Tools console.

Workaround
Manually downgrading to v26.623.41415 fixed the issue immediately.

What steps can reproduce the bug?

right after restart the extension after updated it

What is the expected behavior?

The extension should preserve the existing session or display a Sign in button if authentication is required.

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#29135

Powered by Codex Action

chanfeee · 1 month ago

I have met same issue. But it seems that it has been solved with the version 26.623.70822

emboss · 1 month ago

I seem to face the same issue on Linux Mint 22.2, local VS Code installation (1.128.0). The issues started roughly three weeks ago, I can't remember the exact version. I'm currently using the latest release version 26.707.31428.

The failure is intermittent and affects multiple extension versions. I tried versions from months back and the failure persists. These older versions used to work flawlessly back when they were the latest release version. It is also not related to the VS Code version, there were at least three updates of VS Code in the meantime - all of them showed the same Codex extension behaviour.

Most times, codex app-server starts and the webview remains stuck in the "loading icon state". Other times I see a gray background when it's stuck. And yet other times I don't see any indicator at all and it still remains stuck. In roughly 1 out of 50 tries, it will suddenly load successfully - without having changed or touched anything by me.

Deleting ~/.codex, auth.json and caches does not fix the issue reliably. I've tried disabling/enabling the extension, uninstalling/reinstalling, nothing works to fix it reliably.

Logs repeatedly contain lines such as the following when startup fails:

2026-07-10 22:25:02.530 [error] [CodexMcpConnection] cli: message="2026-07-10T20:25:01.709257Z  WARN
 codex_core_plugins::manager: failed to warm featured plugin ids cache error=remote featured plugin request to
 https://chatgpt.com/backend-api/plugins/featured failed with status 401 Unauthorized:
{\"detail\":\"Unauthorized\"}\n2026-07-10T20:25:02.506739Z
WARN codex_core_plugins::manifest: ignoring interface.defaultPrompt[0]: prompt must be at most 128 characters
path=file:///.../.codex/.tmp/plugins/plugins/ngs-analysis/.codex-plugin/plugin.json\n2026-07-10T20:25:02.509121Z 
WARN codex_core_plugins::manifest: ignoring interface.defaultPrompt[0]: prompt must be at most 128 characters
path=file:///.../.codex/.tmp/plugins/plugins/ngs-analysis/.codex-plugin/plugin.json"

The identical installation may occasionally start successfully after a restart, suggesting an initialization race rather than persistent
local configuration corruption.

I can't seem to identify anything suspicious in VS Code developer tools.

emboss · 1 month ago

Follow-up: I've found two reliable workarounds for my situation:

If I start VS Code with code --disable-gpu , the Codex extension will reliably load and never hang.
Of course, disabling GPU is not desirable. Through trial & error I found out that the issue in my case is path-resolution behavior in VS Code, not extension contents, GPU, authentication, or Codex configuration. If I start VS Code using the default settings, it's freezing up. However, if I specify the exact same extensions folder explicitly with code --extensions-dir "$HOME/.vscode/extensions", then the freezing behaviour will be gone reliably.