codex - 💡(How to fix) Fix High CPU usage in VS Code when opening Codex panel in a non-Git workspace [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20295Fetched 2026-04-30 06:30:31
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Timeline (top)
commented ×2labeled ×2closed ×1
RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

26.422.71525

What subscription do you have?

ChatGPT Pro

Which IDE are you using?

VS Code

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

Opening the Codex panel in VS Code causes CPU usage to spike immediately and remain high. Disabling the Codex extension and restarting VS Code makes CPU usage return to normal.

This appears to happen when the current VS Code workspace is not a Git repository.

Environment:

  • OS/platform: Darwin 25.4.0 arm64 arm
  • VS Code: 1.118.1
  • Codex VS Code extension: [email protected]
  • Architecture: Apple Silicon / darwin-arm64
  • Workspace type: local folder, not a Git repository

Observed high-CPU processes:

  • Code Helper (Renderer): roughly 90% to 200%+
  • Code Helper (Plugin): roughly 30% to 50%

What steps can reproduce the bug?

  1. Open VS Code with a folder that is not a Git repository.
  2. Enable the Codex VS Code extension.
  3. Open the Codex panel/window.
  4. Observe CPU usage in Activity Monitor or VS Code Process Explorer.

What is the expected behavior?

Codex should handle non-Git workspaces gracefully. Opening the Codex panel in a folder that is not a Git repository should not cause sustained high CPU usage, repeated Git metadata requests, or log flooding.

Additional information

No response

extent analysis

TL;DR

Disabling the Codex extension when working with non-Git repositories in VS Code may be a necessary workaround to prevent high CPU usage.

Guidance

  • Verify that the issue is specific to non-Git repositories by testing the Codex extension in a Git repository to see if CPU usage remains normal.
  • Try disabling and re-enabling the Codex extension in a non-Git repository to confirm the extension is the cause of the high CPU usage.
  • If the issue persists, consider reporting the problem to the Codex extension developers, providing detailed steps to reproduce and system specifications.
  • Check for any updates to the Codex extension or VS Code that may address the issue.

Example

No code snippet is provided as the issue seems related to the extension's behavior rather than a specific code implementation.

Notes

The exact cause of the high CPU usage is not specified, but it's clear that the Codex extension is involved, particularly when used in non-Git repositories. Further investigation by the extension developers may be necessary to resolve the issue fully.

Recommendation

Apply workaround: Disable the Codex extension when working with non-Git repositories in VS Code. This is because the extension currently causes high CPU usage in such scenarios, and disabling it mitigates the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING