Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix High CPU usage and overheating on macOS when Codex is active in Antigravity, even with an empty project [7 comments, 5 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#17767•Fetched 2026-04-15 06:28:47
View on GitHub
Comments
7
Participants
5
Timeline
11
Reactions
1
Author
gunesyusuf34gunesyusuf34
Participants
AK25789AK25789github-actions[bot]github-actions[bot]GoXLdGoXLdgunesyusuf34gunesyusuf34sduboissdubois
Timeline (top)
commented ×7labeled ×2closed ×1reopened ×1

Root Cause

I downgraded the Codex extension to a previous version, but the problem remained. This does not seem to be caused by Antigravity alone, because CPU stays normal when Codex is disabled. This does not seem to be caused by project size alone, because the issue also happens with an empty folder. Based on Activity Monitor, the issue appears related to Antigravity Helper (Renderer) / Plugin behavior when Codex is active.

RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

26.409.20454

What subscription do you have?

ChatGPT Plus

Which IDE are you using?

Google Antigravity

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

When Codex is active inside Antigravity on macOS, CPU usage becomes abnormally high and my MacBook heats up significantly.

I tested this multiple times with Activity Monitor and isolated the issue as much as possible. The abnormal load appears when Codex is enabled in Antigravity. In the problematic state, Activity Monitor shows very high CPU usage from these processes:

Antigravity Helper (Renderer) Antigravity Helper (Plugin)

In some cases I observed values like:

Antigravity Helper (Renderer): 285%+ Antigravity Helper (Renderer): 100%+ Antigravity Helper (Plugin): 50%+

When this happens, the machine gets noticeably hot.

I also tested with an empty project folder, and the issue still occurs there, so this does not seem to depend on project size.

What steps can reproduce the bug?

  1. Open Antigravity on macOS.
  2. Enable the Codex extension/plugin.
  3. Open a project folder in Antigravity.
  4. Wait briefly and check Activity Monitor.
  5. Observe very high CPU usage from Antigravity Helper (Renderer) and Antigravity Helper (Plugin).

I also tested these comparison cases:

  • Antigravity closed -> no overheating, no abnormal CPU
  • Antigravity open, no project open, Codex disabled -> normal
  • Antigravity open, no project open, Codex enabled -> normal
  • Antigravity open, project open, Codex disabled -> normal
  • Antigravity open, project open, Codex enabled -> high CPU and overheating
  • Antigravity open, empty project folder open, Codex enabled -> high CPU and overheating again

This suggests the problem is specifically triggered when Codex is active in Antigravity, even if the opened folder is empty.

What is the expected behavior?

CPU usage should remain near idle when no heavy task is running.

Enabling Codex should not cause Antigravity Helper (Renderer) and Plugin processes to consume excessive CPU, especially when the opened folder is empty or when no meaningful task is running.

The app should stay thermally normal during idle or light use.

Additional information

I downgraded the Codex extension to a previous version, but the problem remained. This does not seem to be caused by Antigravity alone, because CPU stays normal when Codex is disabled. This does not seem to be caused by project size alone, because the issue also happens with an empty folder. Based on Activity Monitor, the issue appears related to Antigravity Helper (Renderer) / Plugin behavior when Codex is active.

extent analysis

TL;DR

Disabling the Codex extension in Antigravity may be the most straightforward workaround to prevent high CPU usage and overheating.

Guidance

  • Verify that the issue is indeed caused by the interaction between Codex and Antigravity by disabling Codex and checking CPU usage.
  • Try closing and reopening Antigravity with Codex enabled to see if the issue persists consistently.
  • Consider reporting this issue to the developers of both Codex and Antigravity, as it may be a compatibility problem between the two.
  • If possible, test the same setup on a different platform or with a different IDE to isolate if the issue is specific to macOS or Antigravity.

Example

No specific code snippet is applicable in this scenario as the issue seems to be related to the interaction between the Codex extension and Antigravity IDE rather than a coding problem.

Notes

The fact that downgrading the Codex extension did not resolve the issue suggests that the problem might not be version-specific but rather a compatibility or behavioral issue when Codex is active in Antigravity.

Recommendation

Apply workaround: Disabling the Codex extension when not in use could mitigate the high CPU usage and overheating issue until a more permanent fix is found by the developers.

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…
#model compatibility#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix High CPU usage and overheating on macOS when Codex is active in Antigravity, even with an empty project [7 comments, 5 participants]