[Windows] Severe mouse stuttering after launching Codex Desktop until pet/avatar overlay is opened and closed
What version of the Codex App are you using (From “About Codex” dialog)?
26.810.50856
What subscription do you have?
Team
What platform is your computer?
Windows 11
What issue are you seeing?
[!IMPORTANT] ## Temporary workaround If Codex Desktop causes severe system/UI stuttering: 1. Open the Codex pet/avatar feature. 2. Close or disable the pet/avatar feature again. On my system, the mouse and UI stuttering stops immediately after the pet/avatar overlay is opened once and then closed.
Issue
Simply launching Codex Desktop causes severe system/UI stuttering on Windows 11, including noticeable mouse cursor stutter.
The issue starts immediately after Codex is opened and does not require starting a task.
During investigation, I observed approximately 974 MiB/s (~1 GB/s) of continuous read I/O while Codex is running.
Interestingly, the measured throughput is very close to the bandwidth required for repeatedly processing an uncompressed 4K BGRA/RGBA frame at roughly 30 FPS:
3840 × 2160 × 4 bytes × 30 FPS ≈ 949 MiB/s
What steps can reproduce the bug?
Simply launching Codex Desktop causes severe system/UI stuttering on Windows 11, including noticeable mouse cursor stutter.
What is the expected behavior?
A hidden or disabled avatar/pet overlay should not continuously process/copy full-resolution frames.
Launching Codex should also not generate ~1 GB/s of continuous read I/O or cause system-wide mouse/UI stuttering.
Additional information
Investigation / suspected cause
The logs show that the newer Codex build creates an additional hidden window named:
avatarOverlay
Events also appear to be dispatched to both the main Codex window and this hidden overlay window.
Based on the measured ~974 MiB/s read throughput and the timing/size correlation, it appears that the hidden avatar/pet overlay may still be processing or copying full-resolution desktop/frame data at approximately 30 FPS even when the overlay is not visible.
I have not confirmed this from the Codex source code, so this is currently a suspected cause based on runtime measurements and logs.
Reproduction
- Start Windows 11 normally.
- Confirm that mouse/system responsiveness is normal.
- Launch Codex Desktop.
- Immediately observe significant mouse/UI stuttering.
- Open the Codex pet/avatar feature.
- Disable/close the pet feature.
- The mouse/UI stuttering immediately disappears.
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
OH MY GOD DO YOU KNOW HOW LONG I HAVE BEEN TRYING TO FIGURE OUT WHAT THE FUCK HAPPENED MY MACHINE OVERNIGHT.
I have been plugging cables in and out of everywhere. God damnit. I rebooted and it happened again. I rebooted and didn't open Codex and everything is fine 🙈
I confirm. This is an insanely bad behavior for a "Lightweight" agent...
Opening pet/avatar once and then closing it stop the stuttering for me
Seeing the same issue. Feedback report:
no-active-thread-01a00ae0-8471-7010-afe1-e3d0f92fead3I can independently reproduce this on Windows 11 Home build 26200 with Codex package
26.810.7004.0.The severe system-wide mouse/input freezes last approximately 5–10 seconds and occur despite moderate CPU, memory, GPU, and process-priority usage.
Local window inspection found an invisible top-level
Codexwindow owned byChatGPT.exe, approximately 408×403 pixels. Closing only this hidden window with a nativeWM_CLOSEmessage immediately removed the worst lag while leaving the main Codex window running. Restarting Codex recreated the hidden window and the lag returned.Disabling the
computer-useplugin did not change the behavior. Inspection of the installed app bundle also suggests that the avatar overlay is prewarmed even when the persisted overlay-open state is false.A temporary workaround is a user-level process that closes only this specific invisible overlay window. Please investigate preventing creation of the avatar overlay renderer/window when Pets are tucked away or disabled, and stopping its cursor/input/composition activity while hidden.
Related report: #38711.