codex plugin crashes vscode, can't use the plugin

Resolved 💬 5 comments Opened Jul 17, 2026 by jligeza Closed Jul 17, 2026

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 ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗