Antigravity IDE background npm exec causing Command Prompt window to flash/pop up

Hi everyone,

I am experiencing an annoying issue on Windows 11 Home where a Command Prompt window briefly flashes (opens and immediately closes) on my screen every few minutes.

After digging into my global npm cache log folder, I found that the flashing perfectly aligns with several background npm processes being triggered by Antigravity IDE.

The Culprit Command

According to the logs, the IDE is repeatedly trying to spawn this command in the background:

Bashnpm exec chrome-devtools-mcp@latest --autoConnect --no-usage-statistics --no-performance-crux

Log File Details

This behavior is repeated across multiple log files in my cache, for example:

  • 2026-06-17T01_10_12_783Z-debug-0.log
  • 2026-06-17T01_10_28_774Z-debug-0.log
  • 2026-06-17T01_11_00_422Z-debug-0.log
  • 2026-06-17T01_21_09_698Z-debug-0.log

The logs explicitly show the configuration being loaded from the IDE’s directory path containing .npmrc.

Environment

  • OS: Windows 11 Home Single Language (24H2)
  • Node version: v24.12.0
  • npm version: v11.6.2

It seems like Windows is forcing a visible shell window to spawn every time the IDE executes this Model Context Protocol (MCP) tool.

Is there a known setting within Antigravity IDE to force these background integration checks to run completely silently or hidden? Or is there an environment variable tweak I can apply to prevent npm exec from flashing the cmd window?

Thanks in advance for the help!