›_ Codex Issues
Codex Issues / #33812

codex plugin crashes vscode, can't use the plugin

Resolved 💬 5 comments Opened Jul 17, 2026 by jligeza Closed Jul 17, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the IDE extension are you using?

openai.chatgpt 26.707.91948 (linux-x64); bundled codex-cli 0.144.5

What subscription do you have?

plus

Which IDE are you using?

VS Code 1.129.0 (commit 125df4672b8a6a34975303c6b0baa124e560a4f7), x64

What platform is your computer?

Linux Mint 22.3, kernel 6.17.0-40-generic, x86_64 - Intel Iris Xe (Mesa), 30 GB RAM

What issue are you seeing?

Using the Codex panel repeatedly crashes the entire VS Code window; the renderer exits with reason: clean-exit, code: <unknown>. After reopening it crashes again within ~1-6 minutes while Codex is active. Disabling the Codex extension stops the crashes completely; all other extensions are stable.

main.log (one session):

10:41:00 CodeWindow: renderer process gone (reason: clean-exit, code: <unknown>)
10:42:30 CodeWindow: renderer process gone (reason: clean-exit, code: <unknown>)
10:48:38 CodeWindow: renderer process gone (reason: clean-exit, code: <unknown>)

What steps can reproduce the bug?

  1. Open a workspace with the Codex panel active in VS Code.
  2. Use Codex normally.
  3. After some initial loading is done (like 10 seconds or so), the window dies with clean-exit.
  4. Reopening reproduces it; disabling the Codex extension stops it.

What is the expected behavior?

The Codex panel runs without crashing the VS Code window.

Additional information

Ruled out: not OOM (18-19 GB RAM + 8 GB swap free at crash time); no GPU/i915/drm errors in the kernel log; no native segfault in the journal at crash times; the app-server is healthy (no panic/fatal in ~/.codex/logs_2.sqlite). The renderer death is clean-exit (not a signal/segfault), so Crashpad produces no crash dump.

Tried without success: reinstalling the extension; installing older extension versions (like one week old or 1 month old); deleting ~/.codex; deleting ~/.config/Code. None fixed it.

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 1 month ago

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

  • #33725
  • #33521

Powered by Codex Action

jligeza · 1 month ago

The workaround from this issue fixed the crash, closing the issue as a potential duplicate:
https://github.com/openai/codex/issues/33725

amiras2030 · 1 month ago

I can reproduce the same issue on Ubuntu 24.04 with VS Code 1.129.0 and openai.chatgpt@26.707.91948.

My account is on a ChatGPT Pro subscription, so this does not appear to be limited to accounts.

In my case, an empty VS Code window remains stable. The crash starts as soon as I open a local project or workspace while the Codex extension is enabled.

I also tried:

  • Uninstalling the latest Codex extension version.
  • Installing the previous version, openai.chatgpt@26.707.71524.
  • Completely removing VS Code.
  • Deleting all VS Code caches.
  • Deleting all installed extensions.
  • Deleting global storage and user state.
  • Reinstalling VS Code 1.129.0 from scratch.
  • Installing only the latest OpenAI Codex extension in the clean installation.
  • Testing with no other extensions installed.

The rollback did not fix the issue on my machine.

A completely empty VS Code window opens normally.

However, as soon as I open a local project or workspace while the Codex extension is installed, VS Code crashes with:

The window terminated unexpectedly
(reason: 'clean-exit', code: '0')

Disabling or uninstalling openai.chatgpt immediately fixes the issue, and the same project opens normally.

Environment:

  • OS: Ubuntu 24.04 LTS
  • Architecture: Linux x86_64
  • Desktop session: X11
  • VS Code: 1.129.0
  • Extension: openai.chatgpt@26.707.91948
  • Local workspace
  • Not Remote SSH
  • Not Dev Containers
  • Not WSL
jligeza · 1 month ago

Looks like the vscode has to be started once from bash like code --disable-gpu, and we need to watch a new advertisement of the latest GPT 5.6 model. After this advertisement is gone, the vscode can be launched normally.

I am also using windows 11 on another machine, and also couldn't lanuch codex plugin at first.

amiras2030 · 1 month ago

@jligeza Thanks for sharing this. After updating both VS Code and the Codex extension today, the issue seems to be resolved on my machine and everything is working normally again.