Skip to content

[Bug] Windows Codex Desktop sidebar flickers / renders incorrectly with GPU acceleration enabled #24904

Open

Description

@cloudless798

What issue are you seeing?

Summary

Codex Desktop on Windows has a GPU/hardware-accelerated rendering issue. The left sidebar flickers during assistant thinking/streaming, and in light mode the sidebar becomes extremely dark/low-contrast with white hover rectangles. Launching Codex with GPU disabled / software rendering makes the UI render normally, which strongly suggests the issue is specific to the GPU compositing path.

Environment

  • OS: Windows
  • Codex Desktop package: OpenAI.Codex_26.519.11010.0_x64
  • App release seen in logs: 26.519.81530
  • Electron seen in logs: 42.1.0
  • Workspace: C:\Users\31236\Documents\DZH
  • Display scale: 125% observed in renderer args (--device-scale-factor=1.25)

Reproduction

  1. Start Codex Desktop normally on Windows.
  2. Use light mode.
  3. Observe the left sidebar.
  4. Hover sidebar items.
  5. Send a prompt and wait while the assistant is thinking/streaming.
  6. Switch to dark mode and repeat.
  7. Launch Codex with GPU disabled / software rendering and compare.

Actual Behavior

  • In light mode, the left sidebar renders almost black / very low contrast.
  • Hovering items in the left sidebar shows white rectangular artifacts.
  • In dark mode the sidebar is readable, but the left side still flickers during assistant thinking/streaming.
  • Normal launch shows a GPU process in command line:
    --type=gpu-process
  • At least one log contained:
    Recoverable Chromium child process gone ... processType=GPU reason=killed serviceName=GPU

Expected Behavior

The sidebar should render consistently in light and dark mode, with no flickering or hover artifacts during assistant activity.

Important Finding

When launching Codex with GPU disabled / software rendering, the UI renders normally and the sidebar flicker disappears. This strongly suggests a Windows GPU / hardware acceleration / Chromium compositing issue rather than a project configuration issue.

Things Already Tried

  • Switched between light and dark mode.
  • Cleared Codex GPU/cache state.
  • Installed Git for Windows and fixed PATH.
  • Initialized the workspace as a Git repo.
  • Fixed safe.directory / dubious ownership warnings.
  • Cleared Codex Local Storage / stale feature-flag cache.
  • Restarted Codex multiple times.

These reduced unrelated log noise, but the sidebar rendering/flicker issue persisted under normal GPU-accelerated launch.

Related Public Reports

There appear to be other Windows Codex Desktop UI/GPU/flicker/freeze reports, including:

This report adds the key observation that disabling GPU/software rendering makes the UI normal.

What steps can reproduce the bug?

  1. On Windows, launch Codex Desktop normally.
  2. Use light mode.
  3. Observe the left sidebar: it appears very dark / low contrast.
  4. Move the mouse over items in the left sidebar.
  5. Observe white rectangular hover artifacts.
  6. Send any prompt and wait while the assistant is thinking or streaming a response.
  7. Observe that the left sidebar flickers during assistant activity.
  8. Switch to dark mode.
  9. The sidebar becomes readable, but flickering still occurs during assistant thinking/streaming.
  10. Launch Codex with GPU disabled / software rendering.
  11. Observe that the sidebar renders normally and flickering disappears.

What is the expected behavior?

The left sidebar should render correctly in both light and dark mode, without dark/white hover artifacts, and it should not flicker while the assistant is thinking or streaming a response.

GPU-accelerated normal launch and software-rendered launch should have consistent UI rendering behavior.

Additional information

Hi, I’m seeing a Codex Desktop Windows GPU rendering bug.

In normal launch, the left sidebar flickers during assistant thinking/streaming. In light mode the sidebar becomes almost black/low contrast and hover states show white rectangular artifacts. In dark mode it is readable but still flickers.

Launching Codex with GPU disabled/software rendering makes the UI normal, so this appears to be a Windows GPU / Chromium compositing issue.

Environment:

  • Windows
  • Codex Desktop: OpenAI.Codex_26.519.11010.0_x64
  • Release in logs: 26.519.81530
  • Electron in logs: 42.1.0
  • Display scale: 125%

I already tried clearing cache/Local Storage, installing Git, fixing PATH and Git safe.directory warnings, and restarting. The issue persists only under normal GPU-accelerated launch.

Activity

  1. HuakunShen commented on May 29, 2026

    @HuakunShen

    Same on Mac

  2. neonglobe commented on May 29, 2026

    @neonglobe

    this is causing annotations impossible to use and it takes away context while typing and mouse focus is no longer in the box.
    this is a huge issue

  3. Zogar89 commented on May 30, 2026

    @Zogar89
    Image

    Same here.

  4. MurphyPotato commented on Jun 2, 2026

    @MurphyPotato

    Workaround: Turn off Settings > Appearance > Translucent sidebar. This fixes the issue in both light and dark mode.

  5. NolvusMadeIt commented on Jul 12, 2026

    @NolvusMadeIt

    Follow-up: reproduced on the new ChatGPT desktop package (July 12, 2026)

    I am seeing the same Windows renderer/compositing failure on the newly rebranded ChatGPT desktop app. I used the Codex CLI/workspace agent to inspect the local process tree, Windows Error Reporting, package metadata, and renderer flags.

    Environment

    • Windows 11 Pro, build 26200
    • App package: OpenAI.Codex_26.707.6957.0_x64__2p2nqsd0c76g0
    • Chromium process version reported in WER: 150.0.7871.115
    • GPU 0: NVIDIA GeForce RTX 3060, driver 32.0.16.1074
    • GPU 1: AMD Radeon(TM) Graphics, driver 31.0.21923.11000

    OpenAI's migration guidance says the updated Codex app becomes the new ChatGPT desktop app, which explains why the installed package still identifies as Codex: https://help.openai.com/en/articles/20001276/

    Symptoms and Windows evidence

    The app launched normally but froze and lagged heavily while the rest of Windows remained usable. Windows Application Hang events were recorded for ChatGPT.exe at 15:15:41 and 15:34:17 local time. The latter referenced package OpenAI.Codex_26.707.6957.0.

    The normal launch included a Chromium --type=gpu-process and renderer children. Available physical RAM was low during the initial inspection, but the app-specific Application Hang records and the renderer behavior pointed to a graphics path issue rather than a simple hardware shortage.

    Controlled test

    I stopped only the ChatGPT app process tree and relaunched the same installed executable with:

    --disable-gpu
    

    The app then launched with:

    • GPU child using d3d11-warp-webgl
    • Renderer children using --disable-gpu-compositing
    • All ChatGPT processes reporting responsive
    • No new ChatGPT Application Hang events during verification

    I also cleared only disposable GPU/shader caches (GPUCache, GrShaderCache, DawnWebGPUCache, and DawnGraphiteCache). Conversations, account state, projects, and the installation were preserved.

    Current conclusion

    This strongly implicates the Windows Chromium/Electron hardware-compositing path. Disabling GPU acceleration is a reliable local workaround for this build on this machine. I created a persistent “ChatGPT (GPU Safe Mode)” shortcut so the app continues to launch with the workaround.

    This appears to be a newer-build/rebranded-app continuation of the GPU rendering issue described here, rather than a duplicate symptom report. I hope the newer package/version details and the controlled WARP comparison help narrow the upstream fix.

    I can provide additional sanitized process metadata or WER details if useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions