**Title:** Antigravity ptyhost process (node.mojom.NodeService) stuck at 100% CPU
when running alongside Codex IDE
Environment:
-
Antigravity v1.107.0 (Electron 39.2.3)
-
Codex v26.305.950 (Electron 40.0.0)
-
macOS Darwin 25.3.0
-
Both IDEs running simultaneously
Description:
When Antigravity and Codex (OpenAI’s IDE, also Electron-based with node-pty)
run concurrently, Antigravity’s ptyhost process (node.mojom.NodeService)
enters a 100% CPU spin loop and never recovers, causing all terminal features
to freeze.
Both apps use node-pty for terminal management and hold separate TTY devices
(no direct device conflict), but the ptyhost process still gets stuck. This
issue does not occur when Antigravity runs alone.
Possible cause:
Both IDEs are Electron apps sharing the same Chromium field-trial-handle base
ID (1718379636). Codex’s app-server process also spawns child processes (e.g.,
chrome-devtools-mcp) that may contribute to resource contention. The
combination of two Electron apps with active node-pty sessions appears to
trigger a spin loop in Antigravity’s ptyhost.
Diagnostic data:
Stuck process: PID 55074 - Antigravity Helper (node.mojom.NodeService)
State: R (running, not sleeping) — 100% CPU sustained for 2+ hours
Antigravity PTY devices: /dev/ttys011, /dev/ttys014
Codex PTY devices: /dev/ttys009, /dev/ttys016 (no overlap)
Codex app-server child: npm exec chrome-devtools-mcp@latest
Log: ~/Library/Application
Support/Antigravity/logs/20260306T140524/ptyhost.log
Reproduction:
1. Open both Antigravity and Codex with projects
2. Use integrated terminals in both IDEs
3. After some time, Antigravity’s terminal becomes unresponsive while Codex
remains normal
Workaround: kill <ptyhost_pid> — Antigravity auto-respawns the process and
terminal recovers.