Codex Desktop on macOS drives high GPU only while window is visible; minimizing immediately drops usage
What version of the Codex App are you using?
- Codex Desktop: 26.602.40724
- App bundle version: 3593
- Bundled Codex CLI:
codex-cli 0.137.0-alpha.4 - External/Homebrew Codex CLI:
codex-cli 0.137.0
What platform is your computer?
- macOS 26.5.1 (25F80), Apple Silicon
- Mac mini (Mac16,10)
- Apple M4, 10-core CPU (4 performance + 6 efficiency cores)
- 32 GB memory
- External display: Kuycon G34W, 5120 x 2160 native, 60 Hz
- Current display mode: 2560 x 1080 HiDPI logical resolution
- HDR supported
What issue are you seeing?
Codex Desktop appears to cause very high GPU usage only when its window is visible. When the Codex window is minimized, GPU load drops immediately, while the same session continues running.
This makes long-running Codex work difficult to monitor from the desktop app, especially on a large 5120 x 2160 HiDPI display. The current workaround is to keep Codex Desktop minimized and monitor the session from terminal/session logs instead.
We initially suspected the external HiDPI display setup, but after testing, the trigger appears to be the Codex App window visibility itself:
- Codex window visible: GPU workload rises very high, sometimes close to 100%.
- Codex window minimized: GPU workload immediately drops.
- The project/test workload is not the observed trigger.
This looks like a UI renderer/compositor path, animation, live progress indicator, or HiDPI repaint loop issue rather than agent computation.
Steps to reproduce
- On macOS 26.5.1, launch Codex Desktop 26.602.40724.
- Open a project/session and leave the Codex window visible on an external 5120 x 2160 HiDPI display.
- Observe GPU usage in Activity Monitor or another GPU monitor.
- In this environment, GPU usage can climb very high, sometimes close to 100%.
- Minimize the Codex window without stopping the session.
- Observe that GPU usage immediately drops.
- Restore/show the Codex window and observe that GPU usage rises again.
Expected behavior
Codex Desktop should not drive sustained high GPU usage just because the app window is visible. Keeping a conversation visible for monitoring a long-running task should be low overhead.
Actual behavior
GPU load is high while the Codex window is visible and drops immediately when the window is minimized. The user can only keep GPU load low by minimizing Codex and monitoring session logs/CLI output instead.
Diagnostic notes / isolation
- The same session continues running after minimizing the app, but GPU load drops immediately.
- This suggests the app's visible UI rendering/compositing path is the trigger.
- Large HiDPI display setup may amplify the issue.
- BetterDisplay virtual screen mirroring was previously used for custom HiDPI experiments, but at the time of the current isolation the display was not linked to a BetterDisplay virtual screen (
virtualScreenLinked@Display:2 = 0). - No raw session logs are attached here because they may include local paths/session details.
Related issues
This may be related, but the reproduction here is specifically tied to Codex Desktop window visibility on macOS:
- #16857
- #18545
- #23072
- #13749
10 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Additional observation / 补充观察:
中文
在最新版 Codex Desktop
26.609.41114(发布于 Jun 13, 2026)上,问题仍然很严重,并且我又观察到两个更明确的触发特征:run中的会话时,窗口越大,GPU 占用越高。这进一步说明问题和可见窗口的 UI 渲染面积、实时运行状态的刷新 / repaint / compositor 路径有关,而不像是模型推理、项目测试或后台任务本身导致的。
换句话说:
This also appears distinct from the noisy logging issue discussed in #26843. That fix may reduce long-session logging / disk-write amplification, but it does not seem to resolve this visible-window GPU/compositor issue.
English
Still reproduces severely on Codex Desktop
26.609.41114(released Jun 13, 2026). I have two more specific observations:This makes the issue look even more tied to visible UI rendering area plus live running-session refresh / repaint / compositor work, rather than model inference, project tests, or background agent computation.
In short:
This seems separate from the noisy logging issue mentioned in #26843. That fix may address long-session logging / disk-write amplification, but it does not appear to fix this visible-window GPU/compositor problem.
I can reproduce the same issue on macOS with Codex Desktop
26.616.81150.Environment:
26.526.616.81150149.0.7827.1155120x2880, scale factor 2Observed behavior:
33%.0%.WindowServerand Codex GPU/renderer-related processes as the main visible load.I tested several possible triggers, but none changed the behavior:
This makes my case look less like only the thinking/shimmer animation or pet overlay, and more like the main Codex window visible-rendering/compositor path itself. The strongest signal is:
0%.This also looks related to #24185 because
WindowServeris consistently involved.中文补充:
我这边也复现了同类问题。侧边栏、新空线程、Pet 开关都不影响;只有窗口最小化会让 GPU 立刻从约
33%掉到0%。所以这不像某个聊天内容或 pet overlay,而更像 Codex 主窗口可见时持续触发 macOSWindowServer/ Chromium compositor 重绘。+1, I am experiencing exactly this issue. Here is my detailed report:
I am seeing a reproducible GPU usage issue with the Codex desktop app on macOS 27.0 beta.
Environment:
Issue:
When the Codex desktop window is focused and large/fullscreen, GPU usage immediately jumps to around 85-90%. If I switch focus away from Codex to Finder/Desktop/another app, GPU usage drops quickly to around 10-40%. If I resize the Codex window to a very small size, GPU usage also drops significantly even while Codex remains focused.
This strongly suggests the issue is related to foreground window rendering/compositing in the Codex desktop app, likely Electron/Chromium compositor behavior on macOS 27 beta.
Reproduction steps:
Observed data:
--disable-gpu --disable-gpu-compositing --disable-accelerated-2d-canvasmade the app unresponsive, so that workaround is not usable.Expected behavior:
Codex should not cause sustained 85-90% GPU usage simply by being focused, especially when idle or showing a normal chat/thread view.
Actual behavior:
GPU usage scales heavily with Codex window size and focus state. Large focused Codex window causes very high GPU usage; small window or unfocused Codex significantly reduces GPU usage.
Notes:
This appears separate from other system issues observed on this machine. I also identified unrelated macOS beta issues involving appstoreagent and a third-party screensaver, but the Codex GPU issue reproduces based specifically on Codex window focus and size.
我也遇到了这个问题,看到这贴我才找到了临时解决方案,就是让CODEX窗口最小化,笑死,希望早日修正这个BUG
或者把尺寸缩小
CodeX 在 macOS 上窗口最大化运行时占用的 GPU 都和我本地跑一个 7B 小模型占用的 GPU 资源差不多了,有点夸张。最小化后占用迅速归零。
Same for me. plz fix.
I can reproduce this on an Apple M1 Max (32-core GPU), and the issue persists on a newer build:
I tested focus and visibility as separate states using the AGXAccelerator PerformanceStatistics values:
So focus changes the severity, but does not eliminate the load while the Codex window remains visible. Hiding the window is the only tested state that brings GPU use close to idle.
The hot processes remain the Codex GPU helper (
Codex (Service) --type=gpu-process), the active renderer, and WindowServer. Fresh GPU-helper/renderer process samples and app logs were uploaded privately through Codex feedback.Feedback/session ID:
019f719f-29e1-7d82-86d5-60928330e78bOriginal feedback/session ID:
019f4cdd-bee5-7023-9bc8-1c53aac62c8fHi guys! I found a fix: disable the translucent sidebar (both light and dark modes), and the issue should be gone
<img width="904" height="726" alt="Image" src="https://github.com/user-attachments/assets/425d53ed-bd4c-4cb3-abbb-089ba6fc819c" />