Skip to content

High CPU usage on macOS after updating Codex VS Code extension to 0.50.x+ (0.4.49 works fine) #7972

@voltCore

Description

@voltCore

What version of Codex is running?

Codex 0.4.50+

What subscription do you have?

ChatGPT Plus

Which model were you using?

GPT-5.2 (also reproduced with GPT-5.1)

What platform is your computer?

MacBook with Apple Silicon (M2) MacOS Tahoe 26.2

What issue are you seeing?

After updating the Codex VS Code extension to version 0.50.x +, CPU usage increases significantly on macOS only when a prompt is sent and Codex starts processing it.

While Codex is actively thinking or generating a response, a single process — "Code Helper (Plagin)" — consumes excessive CPU (up to 300–350%) on Apple Silicon.

Image

The editor remains responsive, but system performance degrades noticeably during prompt processing.

Downgrading the extension to version 0.4.49 resolves the issue completely, with CPU usage remaining at normal levels during prompt execution.

What steps can reproduce the bug?

  1. Install Codex VS Code extension version 0.50.x +
  2. Launch VS Code on macOS (Apple Silicon)
  3. Open any project (JavaScript, Python, or mixed)
  4. Open the Codex chat panel and switch agent (Full access) GPT-5.1-Codex-Max High
  5. Enter any prompt and send it
  6. While Codex is processing the prompt, observe system CPU usage in Activity Monitor

Result:
During prompt processing, the "Code Helper (Plugin)" process spikes to 300–350% CPU and my laptop freezing

Workaround:
Downgrading the extension to version 0.4.49 eliminates the high CPU usage during prompt processing.

What is the expected behavior?

During prompt processing, Codex should utilize system resources efficiently and keep CPU usage within reasonable limits.

CPU usage should scale proportionally to the complexity of the prompt and should not saturate multiple CPU cores on Apple Silicon for simple or medium-sized requests.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingextensionIssues related to the VS Code extensionregressionBehaviors that worked in previous versions but were broken due to an update

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions