openai / openai/codex

Windows ChatGPT/Codex app UI turns black when hovering menu — fixed by --disable-gpu-compositing

Open
#44,310 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

Version 26.903.61454

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The new ChatGPT/Codex Windows desktop app has a rendering issue where part of the interface turns black, preventing me from accessing the ChatGPT/Codex selector/menu.

Repairing the app temporarily fixes the issue. After a repair, the application launches and renders normally, but as soon as I move my mouse over the ChatGPT/Codex menu area, the interface turns black again.

I tested several Chromium/Electron launch flags and was able to isolate the issue to GPU compositing.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a0880e-a9f3-75d2-8b4b-0f01c62ffffc

What is the expected behavior?

The ChatGPT/Codex menu should render normally when hovered or opened, allowing me to switch between ChatGPT and Codex.

Additional information

Workaround discovered:

Launching the application with:

--disable-gpu-compositing

completely resolves the issue.

I isolated this by testing the following:

Full workaround — works:
Powershell:
Get-Process ChatGPT,Codex -ErrorAction SilentlyContinue | Stop-Process -Force

$pkg = Get-AppxPackage -Name 'OpenAI.Codex' | Sort-Object Version -Descending | Select-Object -First 1

Start-Process (Join-Path $pkg.InstallLocation 'app\ChatGPT.exe') -ArgumentList '--disable-gpu','--disable-gpu-compositing','--disable-direct-composition','--disable-features=EnableTransparentHwndEnlargement,CalculateNativeWinOcclusion','--force-color-profile=srgb'

I then removed the GPU-disabling flags while keeping the other rendering flags. The black-screen issue returned.

I added back only --disable-gpu-compositing, and the application worked normally.

Finally, I tested only:
Powershell:
Get-Process ChatGPT,Codex -ErrorAction SilentlyContinue | Stop-Process -Force

$pkg = Get-AppxPackage -Name 'OpenAI.Codex' | Sort-Object Version -Descending | Select-Object -First 1

Start-Process (Join-Path $pkg.InstallLocation 'app\ChatGPT.exe') -ArgumentList '--disable-gpu-compositing'

This also works normally. I can hover the menu, open it, and access Codex without the interface turning black.

This appears to isolate the problem specifically to the application's GPU compositing/rendering path rather than corrupted application data.

System information:

OS: Windows 11
GPU: NVIDIA GeForce RTX 5090
Display: 4K / 240 Hz
Installation: Microsoft Store/AppX version of the new ChatGPT/Codex application

Additional information:

Windows' Repair option causes the app to render normally on the first launch, but the problem immediately returns when hovering over the affected menu. --disable-gpu-compositing has been consistently successful and does not require --disable-gpu. Launching the app with the following .bat results in a successful launch with UI rendering normal:
@echo off
powershell -NoProfile -WindowStyle Hidden -Command "Get-Process ChatGPT,Codex -ErrorAction SilentlyContinue | Stop-Process -Force; $pkg = Get-AppxPackage -Name 'OpenAI.Codex' | Sort-Object Version -Descending | Select-Object -First 1; Start-Process (Join-Path $pkg.InstallLocation 'app\ChatGPT.exe') -ArgumentList '--disable-gpu-compositing'"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the hover failure in the Windows Store/AppX app through the ChatGPT.exe entry point on the reported Windows and NVIDIA setup. Compare the menu rendering with and without --disable-gpu-compositing, then trace the affected desktop rendering path. Done means the ChatGPT/Codex selector remains usable when hovered without requiring the workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.