Windows Desktop UI stutters on launch, new chat, first typing, and Settings
What version of the Codex App are you using (From "About Codex" dialog)?
Version 26.616.81150 • Released 23 Jun 2026
Observed installed package:
OpenAI.Codex 26.616.10790.0
App server version in logs: 0.142.0
What subscription do you have?
5x Pro
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
Windows 11 Pro, build 26200
CPU: AMD Ryzen 5 5600X, 6 cores / 12 logical processors
GPU: AMD Radeon RX 7600
GPU driver: 32.0.31021.1015
Power plan: High performance
What issue are you seeing?
Codex Desktop repeatedly causes brief UI/cursor/input stutters during first-use interactions:
- On opening Codex, the cursor/UI stutters briefly, then becomes smooth.
- On opening a new chat, the same stutter happens, then becomes smooth.
- In a new chat, the first typed characters appear, then the UI freezes briefly, then typing is smooth.
- Opening Settings also causes a brief stutter, then becomes smooth.
This reproduces after a fresh reinstall and after deleting Codex data.
Local diagnostics suggest the stutter correlates with Codex Desktop process CPU and memory spikes, not disk, GPU, WMI, Defender, or WSL:
30 second diagnostic capture while reproducing:
Main Codex.exe process:
CPU used: ~18.4 CPU seconds
Peak working set: ~1.1 GB
Peak private memory: ~1.9 GB
Codex app-server process:
CPU used: ~5.05 CPU seconds
Renderer process:
CPU used: ~4.61 CPU seconds
Counters:
Codex process CPU peaked around 147.7% processor time
Total system CPU peaked around 40.18%
Physical disk time peaked around 5.23%
WMI Provider Host CPU stayed low, max around 4.67%
Codex GPU process GPU utilization stayed below 1%
Sanitized relevant Codex Desktop log excerpts:
initialize_handshake_result durationMs=69 outcome=success
window main frame finished load startupElapsedMs=95
window ready-to-show startupElapsedMs=111
[startup][renderer] app routes mounted after 4058ms
method=mcpServerStatus/list durationMs=1914
method=mcpServerStatus/list durationMs=1468
[git] [git-origins] worker-complete dirCount=6 elapsedMs=635
[git-repo-watcher] Starting git repo watcher
error [wsl] error retrieving eligible distro error="Error: Command failed: wsl.exe --status ..."
Note: WSL_DISTRO_NAME is unset in Process/User/Machine env. WSL is not installed, but wsl.exe --status completes locally in about 34ms, so this does not appear to explain the full stutter by itself.
What steps can reproduce the bug?
- Start Codex Desktop on Windows.
- Observe brief cursor/UI stutter after launch, followed by smooth behavior.
- Open a new chat.
- Observe another brief stutter, followed by smooth behavior.
- Type a few characters in the new chat.
- The first characters appear, then the UI briefly freezes/stutters, then typing is smooth.
- Open Settings.
- Observe another brief stutter, followed by smooth behavior.
This reproduces consistently on this machine and also reproduced immediately after a fresh reinstall with Codex data removed.
What is the expected behavior?
Codex Desktop should remain responsive during launch, new chat creation, first typing in a new chat, and opening Settings. Startup/background initialization should not block mouse/cursor movement or text input.
Additional information
Local mitigations tried without improvement:
- Fresh reinstall and deleting Codex data.
- Verified
WSL_DISTRO_NAMEis not set. - Temporarily disabled plugins/MCP/notify via diagnostic minimal config.
- Temporarily disabled sidebar PR icons and removed a broad trusted home-directory project.
- Temporarily disabled/cleared desktop global state for global dictation hotkey, mobile connected state, Chrome extension sync management, saved workspace roots, project order, active workspace roots, and avatar overlay.
- Rotating session/log files was considered but is unlikely to be root cause because the issue reproduced immediately after fresh install.
Diagnostics were collected with a local PowerShell sampler that recorded process CPU/memory, Windows counters, GPU counters, WMI activity, and Codex Desktop logs. I can provide a further-sanitized subset if helpful, but I am not attaching raw logs because they may contain local paths, thread IDs, and prompt history.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗