[Windows] Mouse becomes severely laggy while Codex is thinking
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Title:
[Windows] Mouse becomes severely laggy while Codex is thinking
Description:
The Codex desktop app causes severe mouse input lag while it is in the thinking state. The cursor feels delayed and floaty. The issue happens consistently during thinking and improves after the response finishes.
Reproduction steps:
- Open the Codex desktop app.
- Send a request that keeps Codex in the thinking state for several seconds.
- Move the mouse while Codex is thinking.
- Observe severe cursor delay and stuttering.
- After the response finishes, mouse responsiveness improves.
Expected behavior:
Codex should not affect system-wide mouse responsiveness while generating a response.
Actual behavior:
Mouse movement becomes delayed and feels floaty whenever Codex is thinking.
Environment:
- Windows desktop
- Codex version: 26.814.5167.0 x64
- NVIDIA GeForce RTX 2060
- Intel UHD Graphics 630
- NVIDIA driver: 32.0.15.9144
- Intel driver: 27.20.100.8729
- Oray virtual display driver is installed
Diagnostics:
- Overall CPU usage did not reach 100%; observed peak was about 35%.
- Memory usage was about 57%.
- DPC time stayed around 1% or lower.
- Codex renderer memory reached approximately 400 MB.
- Codex GPU process used approximately 10% to 19% GPU.
- The issue is not resolved by restarting Codex, closing other applications, exiting remote-control software, lowering the Codex GPU process priority, or launching with --disable-gpu.
Additional information:
GPU forcing between RTX and Intel has not yet been tested. Session ID from the in-product feedback submission:
Codex task/thread ID: 01a018d3-76fc-7342-bce4-8c2b840ce918
Feedback session ID: Not available
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the lag on Windows using the listed Codex version and hardware while a request remains in the thinking state. Profile the desktop app during reproduction, then verify that mouse responsiveness remains normal while Codex generates a response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100