›_ Codex Issues
Codex Issues / #31531

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

Open 💬 4 comments Opened Jul 8, 2026 by Fritz07
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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 ↗

4 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #30527
  • #30345

Powered by Codex Action

Fritz07 · 1 month ago

Update: I want to clarify the version timeline.

The issue first started after updating Codex desktop to:

  • Version 26.623.141536
  • Released Jul 6, 2026

After I opened this GitHub issue, the problem seemed to improve temporarily while still on that older updated version. About one day later, CPU usage dropped back down to around 4–5%, memory usage dropped, and laptop core temperature stayed closer to around ~56°C.

Today I updated Codex desktop again to the newer release:

  • Powered by Codex & OWL
  • Version 26.707.31123
  • Released Jul 9, 2026

I updated so I could access GPT-5.6. After installing Version 26.707.31123, the same issue returned.

Current behavior after updating to Version 26.707.31123:

  • CPU usage and temperature are rising again.
  • Core Temp is showing cores around 67–72°C while Codex/GitHub/Chrome are open.
  • Windows becomes sluggish again.
  • AVG repeatedly shows a Behavior Shield alert at the beginning of prompts sent to Codex.

AVG detection details:

  • Threat name: IDP.HELU.PSE80 - Command line detection
  • Process: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
  • Detected by: Behavior Shield
  • Status: Blocked
  • Timing: The popup appears when Codex begins processing a prompt.

Expected behavior:

Codex should not cause sustained CPU/disk/memory spikes, excessive heat, sluggish Windows behavior, or repeated antivirus PowerShell behavior detections when starting a prompt.

Additional note:

This appears to be related to the recent Codex desktop updates. The issue first appeared on Version 26.623.141536, seemed to improve temporarily, and then returned after installing Version 26.707.31123.

I am attaching screenshots showing:

  • Core Temp readings
  • AVG Behavior Shield PowerShell detection

<img width="423" height="479" alt="Image" src="https://github.com/user-attachments/assets/39b94dd7-54f5-4440-a476-2cadd59f9f83" />

<img width="765" height="735" alt="Image" src="https://github.com/user-attachments/assets/6bcd457d-c0fe-4c29-9c52-3dd4945cdb22" />

Fritz07 · 1 month ago

Additional update with AVG scan/quarantine details:

I paused Codex during the AVG deep scan by ending Codex from Task Manager.

AVG deep scan result:

  • AVG reported: “All gone! We’ve safely removed the malware…”
  • Threat name shown after scan: Other:Malware-gen [Trj]
  • Infected file path shown by AVG starts with:

C:\Windows.old\Users\fritz\AppData\Local\Wind...

  • Status: Moved to Quarantine

I then opened AVG Menu → Quarantine and found multiple quarantined items. Some appear to be older items from C:\Windows.old and old 2023 detections, but there are two entries worth noting:

Recent quarantine entry from the scan:

  • File: apps.crx
  • Original location:

C:\Windows.old\Users\fritz\AppData\Local\WindowsApp...

  • Threat name:

Other:Malware-gen [Trj]

  • Time found:

7/9/26, 10:46 PM

PowerShell quarantine entry:

  • File: powershell.exe
  • Original location:

C:\Windows\System32\WindowsPowerShell\v1.0\powers...

  • Threat name:

IDP.HELU.PSE80%_cmd

  • Time found:

7/9/26, 6:35 PM

Recent AVG popup ID:

  • 134041dc9020/2026-07-10T07:17:32.892Z

After the scan finished, I attempted to open Codex again. Codex first failed to open and showed an option to “Check for update.” I selected “Check for update.” After waiting and seeing Codex still did not open, I ended Codex again from Task Manager.

After that, I opened Codex again. This time Codex loaded, but AVG immediately showed the same PowerShell Behavior Shield alert again.

Repeated AVG alert after opening Codex:

  • Threat name: IDP.HELU.PSE80 - Command line detection
  • Process: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
  • Detected by: Behavior Shield
  • Status: Blocked
  • Timing: Appears when Codex opens or begins processing activity

Important note:
The AVG scan quarantined an item under C:\Windows.old at 7/9/26, 10:46 PM, but the repeated PowerShell Behavior Shield alert still happens after opening Codex. So even after quarantine, Codex continues to trigger AVG’s PowerShell command-line detection.

I am attaching screenshots of:

  • AVG deep scan result
  • AVG Quarantine list showing the apps.crx / Other:Malware-gen [Trj] entry and the powershell.exe / IDP.HELU.PSE80%_cmd entry
  • The repeated AVG PowerShell threat secured popup after opening Codex

<img width="1178" height="790" alt="Image" src="https://github.com/user-attachments/assets/7ef64c01-7a07-49bb-81e0-39715d3cbacf" />

<img width="766" height="516" alt="Image" src="https://github.com/user-attachments/assets/1d3f117c-c88c-4abc-9db7-6855d0155408" />

<img width="1168" height="791" alt="Image" src="https://github.com/user-attachments/assets/ebe1fbbe-b445-4fb9-9998-f74a96d98b5a" />

Fritz07 · 1 month ago

Additional security/repair update:

I ran Windows repair commands after AVG repeatedly flagged PowerShell when Codex opened or processed prompts.

DISM result:

  • The restore operation completed successfully.

SFC result:

  • Windows Resource Protection found corrupt files and successfully repaired them.

I then enabled Microsoft Defender Periodic scanning and ran the Defender scan path from Windows Security. The PC rebooted. After Windows came back up, I did not receive any Defender malware warning.

Windows Security currently shows:

  • Current threats: No current threats.

Windows Security Protection History does not show a new Defender malware detection from the reboot scan. It only shows a settings warning related to potentially unwanted app blocking.

AVG Quarantine still shows:

  • apps.crx / Other:Malware-gen [Trj] / 7/9/26, 10:46 PM / under C:\Windows.old...
  • powershell.exe / IDP.HELU.PSE80%_cmd / 7/9/26, 6:35 PM / under C:\Windows\System32\WindowsPowerShell\v1.0\...

I have not restored anything from AVG Quarantine.