Skip to content

CPU Temp Spikes after coding #16185

@texxasrulez

Description

@texxasrulez

Summary

When Codex finishes a coding task in VS Code, CPU usage spikes immediately afterward and CPU temperature rises noticeably. This is reproducible across every project I work on, not just one repository.

The spike happens after Codex completes its work, not only while it is actively generating or editing.

Environment

  • OS: Linux Mint 22.3 (Zena)
  • Kernel: Linux 6.8.0-106-generic
  • Architecture: x86_64
  • VS Code: 1.113.0
  • VS Code commit: cfbea10c5ffb233ea9177d34726e6056e89913dc
  • Codex/OpenAI VS Code extension: openai.chatgpt@26.325.31654

Scope

This happens across all repositories/projects I work on.

Steps to reproduce

  1. Open any project in VS Code.
  2. Disable all other extensions except the OpenAI/Codex extension.
  3. Use Codex to perform a coding task or edit files.
  4. Wait until Codex finishes.
  5. Observe CPU usage and CPU temperature immediately afterward.

Expected behavior

After Codex completes a task, CPU usage should settle back toward normal editor idle/background levels.

Actual behavior

Immediately after Codex finishes, CPU usage spikes and CPU temperature rises noticeably.

What I checked

  • I disabled all other extensions during testing.
  • The problem still occurs.
  • It is reproducible across all projects, not just one codebase.
  • The spike is tied to task completion timing.

Additional notes

This does not appear to be specific to a single repository, language, or project setup.

The pattern suggests some post-task activity triggered by the extension or a helper process it launches after edits complete, such as:

  • workspace scanning
  • diffing/patch finalization
  • indexing
  • other extension host background work

If helpful, I can provide process-level observations from VS Code Process Explorer in a follow-up comment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingextensionIssues related to the VS Code extension

    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