Windows 10 Codex app high CPU/disk usage while idle after recent update

Open 💬 4 comments Opened Jul 8, 2026 by Fritz07

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.623.141536 • Released Jul 6, 2026

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

Environment:

  • Windows 10
  • Platform output:

[Microsoft Windows NT 10.0.19045.0 x64]

  • Codex desktop app version:

[Version 26.623.141536 • Released Jul 6, 2026]

  • ChatGPT Pro plan
  • CPU: Intel Core i7-6700HQ
  • 4 cores / 8 threads
  • Antivirus/security software: AVG + Malwarebytes
  • Project folder: large local Next.js / Node real-estate-system project

Problem:
After a recent Codex desktop app update, opening Codex and opening my local project folder appears to cause high CPU and disk usage even when no Codex task is running.

Observed:

  • Codex shows about 19–32 processes in Windows Task Manager.
  • Total CPU rises to around 69%–91%.
  • Codex itself uses around 20%–24% CPU while apparently idle.
  • Disk usage sometimes reaches 100%.
  • Codex uses around 700–900 MB memory.
  • AVG Software Analyzer also spikes while Codex is open, which may indicate scanning activity triggered by Codex/project access.
  • Laptop CPU temperatures rise to about 70–80°C, with recorded max spikes up to 98°C in Core Temp.
  • Windows dragging/restoring becomes slow.
  • Desktop Window Manager and Windows Explorer also show high CPU during the issue.
  • Problem improves after ending Codex in Task Manager.

Steps to reproduce:

  1. Restart Windows.
  2. Open Task Manager and Core Temp.
  3. Open Codex desktop app.
  4. Open the local Next.js / Node project folder.
  5. Do not start a Codex task, build, test, or terminal command.
  6. Watch CPU, disk, Codex process count, AVG activity, Desktop Window Manager, Windows Explorer, and CPU temperature.

Expected:
Codex should remain mostly idle when no task/build/test/terminal command is running.

Actual:
Codex continues using noticeable CPU/disk while idle, creates many helper processes, triggers high system load, and contributes to high laptop temperatures.

Notes:

  • Node.js JavaScript Runtime was visible but not using significant CPU in Task Manager during one screenshot.
  • The issue seems tied to Codex being open with the local project folder, not an active npm/Next.js dev server.
  • I understand multiple helper processes may be normal for desktop apps, but the concern is the sustained CPU/disk/power usage while idle.

Attachments:

  • Task Manager screenshots
  • Core Temp screenshots
  • Codex version screenshot or version number
  • PowerShell platform output

What steps can reproduce the bug?

Feedback ID: no-active-thread-019f4089-0732-7cd2-9bf6-2933712a051d

What is the expected behavior?

When the Codex desktop app is open but no task is running, it should remain mostly idle and use minimal system resources.

Expected behavior:

  • Codex should not create a large number of active processes while idle.
  • CPU usage should stay low when no prompt/task is running.
  • Disk usage should remain low and should not spike to 100% just from opening Codex.
  • Codex should not cause Windows Explorer, Desktop Window Manager, AVG Software Analyzer, or other background services to spike.
  • The laptop should remain responsive, with normal window dragging, minimizing, and restoring behavior.
  • CPU temperature should stay near normal idle/light-use levels instead of rising quickly toward 70–80°C.
  • Opening a local project folder should not overload the system when Codex is not actively analyzing, building, or running commands.

Additional information

<img width="940" height="786" alt="Image" src="https://github.com/user-attachments/assets/a769d6cf-3e42-4034-afdf-fcf6c3f18ed6" />

<img width="422" height="480" alt="Image" src="https://github.com/user-attachments/assets/51e931f9-ec2c-4611-8215-fed04412709c" />

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗