Windows: pet/avatar overlay makes task switching and mouse dragging freeze
Summary
On Windows, opening the Codex pet/avatar overlay causes severe UI stuttering. Switching tasks from the sidebar becomes laggy, and mouse dragging can become nearly unresponsive while the pet overlay is open.
Steps to reproduce
- Open Codex desktop on Windows.
- Enable or open the pet/avatar overlay.
- Switch repeatedly between tasks in the left sidebar.
- Try to drag the mouse or interact with the window.
Actual behavior
- Task switching stutters or freezes.
- Mouse movement/dragging becomes difficult or temporarily unresponsive.
- The issue persists after restarting Codex.
- It reproduces with Clash TUN disabled and Windows system proxy enabled, so it is not specific to TUN mode.
Expected behavior
The pet overlay should not affect sidebar task switching, mouse input, or desktop UI responsiveness.
Environment
- Codex desktop: 26.707.12708.0
- OS: Windows 11 x64
- GPU: NVIDIA GeForce RTX 5060 Laptop GPU + Intel integrated graphics
Relevant diagnostics
The desktop log reports an unhandled rejection during avatarOverlay initialization:
A dynamic link library (DLL) initialization routine failed.
@worklouder/wl-device-kit/.../@serialport/bindings-cpp/build/Release/serialport.node
Windows Application Error also repeatedly records:
ChatGPT.exe
Exception code: 0xc06d007f
During the affected session, local capability refreshes were also unusually slow:
mcpServerStatus/list: 17,916 msplugin/list: 16,948 msapp/list: 12,795 ms
Normal conversation data reads were much faster (typically around 270 ms), suggesting the stall is associated with overlay/native-module or capability initialization rather than loading the conversation itself.
Additional notes
The Microsoft Visual C++ runtime is installed and current. No full logs are attached because they may contain local paths or conversation metadata.
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Additional isolation results from my Windows setup:
This suggests that the Pet/avatarOverlay rendering itself is sufficient to trigger the stutter, separately from the earlier ESET/serialport crash issue.
Expected behavior:
Keeping a Pet visible should not degrade cursor movement or desktop UI responsiveness.
Have this issue aswell
26.715.2305.026200.8875This appears consistent with the Pet/avatar overlay triggering periodic system-wide input stalls specifically while an agent task is active. In my case, it is not limited to slow rendering or task switching within the Codex window.
Expected behavior:
Keeping the Pet visible while a task runs should not interrupt physical mouse input or degrade responsiveness elsewhere in Windows.
I’m experiencing the same severe mouse lag and performance problems when Codex Pets is enabled.
My system is a Windows 11 desktop/tower PC with an NVIDIA RTX 5080, Intel Core Ultra 9 processor and 32 GB DDR5 RAM. This is a dedicated desktop GPU rather than a laptop with hybrid graphics. Disabling the pet resolves the problem.
Also reproducing on Windows with Codex Desktop package
26.715.4045.0.In this case the pet was enabled unintentionally because the account menu shifted while trying to click Remaining usage (the UX path discussed in #32069). Once the pet appeared, the computer became noticeably laggy.
This links the performance problem to a frequent account-menu action: a layout-shift misclick can enable an overlay that immediately degrades system responsiveness. Expected behavior is that the pet overlay should not make the computer lag, and users should be able to disable the pet entry persistently.
Additional Windows data point: the pet/avatar overlay can still affect mouse input even after it appears to be disabled/hidden.
Environment:
26.715.4045.0ChatGPT.exefile version:150.0.7871.1242620032.0.16.1074, primary display2560x1440 @ 299 Hz32.0.21043.19003Observed behavior:
ChatGPT.exeshowed a hidden Electron/Chromium window that looked like the pet overlay:CodexChrome_WidgetWin_1408 x 400falseChatGPT.exeprocesspet,avatar, oroverlayprocess; the residual overlay window was insideChatGPT.exe.Isolation result:
WM_CLOSEonly to that hiddenCodex408x400 window removed it from the window list.ChatGPT.exe/ Codex stayed running.This suggests the UI toggle may hide the pet/avatar overlay window without destroying it, and the hidden overlay window can still participate in Chromium/GPU/DWM/input handling enough to cause system-wide mouse stalls.
One extra note: this machine also had many MCP/tool child processes at the time, but the stutter stopped after closing only the hidden pet window, without killing the main app or changing MCP configuration. So the hidden overlay window appears to be independently capable of triggering the lag on this setup.