Codex windows app 26.527.31326 fullscreen focused window becomes transparent
What version of the Codex App are you using (From “About Codex” dialog)?
26.527.31326
What subscription do you have?
ChatGPT Free
What platform is your computer?
Windows 10.0.19044 x64
What issue are you seeing?
After the latest Codex Windows app update, Codex has a fullscreen rendering issue.
When the Codex window is fullscreen/maximized and focused, part of the app becomes visually transparent and the Windows desktop icons show through the Codex window.
If I click the Windows taskbar so Codex loses focus, the window renders normally again. When I click back into Codex, the issue returns.
This did not happen on the same computer with previous Codex versions.
Transparency effects are disabled in Windows, but the issue still happens.
What steps can reproduce the bug?
- Open Codex Windows app.
- Maximize/fullscreen the Codex window.
- Click inside Codex so the app is focused.
- Observe that part of the Codex window becomes transparent and the desktop shows through.
- Click the Windows taskbar so Codex loses focus.
- Observe that Codex renders normally while unfocused.
- Click Codex again.
- The transparency/rendering issue returns.
What is the expected behavior?
Codex should render normally while fullscreen/maximized and focused.
Additional information
GPU: AMD Radeon HD 8950
GPU driver: latest available
Display: 1920x1080, 100% scaling
OS transparency effects: disabled
This looks like a Windows/Electron/Chromium GPU compositing regression in the recent Codex Windows app update, possibly related to fullscreen focused rendering. It does not look like a missing Visual C++/.NET runtime issue because the app launches and works normally except for this fullscreen focused rendering problem.
<img width="1920" height="1042" alt="Image" src="https://github.com/user-attachments/assets/459b7b87-bbcb-43ad-9740-77c99a9b76e9" />
<img width="1920" height="1039" alt="Image" src="https://github.com/user-attachments/assets/f4f02efa-8982-431d-9705-5f4e8bd26af4" />
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗