Antigravity users report endless terminal pop-ups after the latest update on Windows

Google Antigravity version 1.19.4 is causing real headaches for Windows users. After the forced update rolled out earlier today, several users have been hit with a disruptive bug that’s causing PowerShell and CMD windows to keep popping up on screen every few seconds.

A couple of threads on r/google_antigravity are full of people sharing the same frustration. One Redditor said, “Imagine this with 10 agents. It makes my entire PC completely unusable.”

Another post has a screenshot showing new CMD windows taking over the screen every time a new project starts. Several users admitted they initially thought their machine had been hit with malware.

The bug doesn’t just affect MCP users either. Even people who have MCP disabled are seeing CMD flashes whenever an agent runs a command, and since the terminal steals focus each time, doing anything else while an agent is running is basically impossible. CPU usage is also reportedly sitting near 90% consistently after the update.

That said, there are actually two separate issues at play here, not one.

According to a detailed breakdown on the Google AI Developer forum, the pop-ups have two distinct causes. The first is tied to MCP server startup: mcp_config.json uses npx.cmd which Windows executes via cmd.exe, spawning a visible console window for each server. With eight MCP servers running, that’s eight popups right at launch.

The second issue is deeper: language_server_windows_x64.exe in v1.19.4 spawns powershell.exe without the CREATE_NO_WINDOW flag, meaning every single run_command execution opens a new terminal window. That one can’t be fixed through configuration alone. It needs an updated binary from Google.

The good news is that the MCP startup popups can be fixed manually.

Replacing npx.cmd with a direct path to node.exe in mcp_config.json bypasses the batch script entirely and eliminates those eight startup windows. The run_command popups, though, will keep appearing until Google ships a patched binary.

That’s not the only thing broken in this update either. A separate report flagged that the agentic browser tool has stopped launching entirely in 1.19.4. A verified Google employee responded in that thread, confirmed the bug, and said a fix was in the works.

For users who just want things working again, rolling back to v1.18.4 is an option, but Antigravity auto-updates almost immediately. To hold it back, delete the ~164MB update file in %LOCALAPPDATA%\Temp\antigravity-stable-user-x64, then go into settings, search “update,” and switch Update Mode to Manual.

Meanwhile, we’ll keep an eye out for any further developments and will update the article accordingly.

If this feels like yet another rough week for Antigravity users, it kind of is. Earlier, we covered how Google’s Antigravity crackdown on OpenClaw had some people reporting their whole Google accounts being disabled. But later, a Google executive clarified it was Antigravity access being blocked amid a spike in “malicious usage” reports.

Featured image credit: u/Any_Surprise_233 / Reddit

We stand out from the tech-media crowd because we break news stories; we mainly bring you stuff that you won’t find anywhere in the mainstream tech media. Our stories have been picked up by some of the world’s most popular websites and media outlets—more info is available here.