Since the February 26th update, numerous terminals are unexpectedly appearing, likely due to remnants from previous projects when initiating antigravity. The CPU usage is consistently near 90%. Each command execution triggers the opening of a new terminal window.
yep can we not revert back to two previous versions? I’m going to try
Root Cause Analysis
The popup issue stems from two distinct underlying causes:
Issue 1 — MCP Server Startup (8 popups on launch)
Cause:
The mcp_config.json file employs the following command:
"command": "npx.cmd"
On Windows systems, .cmd files are executed via cmd.exe, which invariably generates a visible console window.
Reasoning:
Each initiation of the MCP server triggers a batch script, resulting in Windows opening a console window. Consequently, with eight servers, eight popups are produced.
Issue 2 — run_command Execution (1 popup per command)
Cause:
The language_server_windows_x64.exe (Go binary v1.19.4) spawns powershell.exe without the CREATE_NO_WINDOW (0x08000000) flag.
This constitutes a defect at the binary level and is not amenable to resolution through configuration.
This issue is recognized in Antigravity language server v1.19.4 on Windows.
Resolution necessitates an updated binary from Google/DeepMind.
Solution for Issue 1 (Eliminates 8 Startup Popups)
Modify mcp_config.json to substitute npx.cmd with direct Node execution.
Replace:
"command": "npx.cmd",
"args": [
"-y",
"..."
]
With:
"command": "C:\\Program Files\\nodejs\\node.exe",
"args": [
"C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npx-cli.js",
"-y",
"..."
]
Rationale:
node.exe executes a JS file directly, bypassing the batch script and, consequently, the console window.
Issue 2 (Workaround Only)
No configuration-level solution is available.
Options:
-
Update Antigravity (check for version > 1.19.4)
-
Minimize
run_commandusage -
Report bug referencing:
language_server_windows_x64.exe missing CREATE_NO_WINDOW
Verification Steps
- Apply the
mcp_config.jsonchange - Restart Antigravity
- Confirm: No CMD windows appear at startup
- Run
run_command→ One popup may still appear (pending binary fix)
4 Likes
@NeoNerd this totally makes sense b/c i did set up 9 MCP servers. Learned about them over the weekend. I’m no developer but i learn quick lol. I try to pay attention to everything Antigravity does as things fly by so I do believe this will resolve issue 1. I also think the workaround will resolve issue 2 as well. Now If i could just figure out how to get my chat history back or at least to stop the agent from sitting there in a constant spin trying to bring the history up (certain one’s not all of them) then I think I”ll be good until the next release. Question: if the agent is just sitting there spinning trying to load chat history, then I’m assuming it’s burning through tokens yes? Asking b/c I have built a Modal dashbord via Firebase that works great but I went from 20% usage to 80% in less than 2 hours b/c i was trying to get Antigravity to fix the popups etc in a new chat. I’m now wondering if it was spinning and thinking b/c the MCP servers weren’t started.
I’d like to share an additional finding regarding the recent update to this Agent-First IDE. Aside from the terminal popups, there is also a significant change in the default shell being executed.
It appears that v1.19.4 switched the background execution from PowerShell Core (pwsh.exe) back to the legacy Windows PowerShell (powershell.exe).
Here are the updated logs from my testing, which now directly include the executable file versions for clarity:
In v1.18.4:
The tool utilizes PowerShell Core (pwsh.exe, version 7.5.4).
> Write-Host "=== PowerShell Version ==="; Get-Host | Select-Object Version | Out-Host; Write-Host "=== PowerShell Path ==="; (Get-Process -Id $PID).Path | Out-Host; Write-Host "=== Antigravity Version ==="; Antigravity -v; (Get-Item "$(Split-Path (Get-Command Antigravity).Path)\..\Antigravity.exe").VersionInfo.FileVersion
=== PowerShell Version ===
e[32;1mVersione[0m
e[32;1m-------e[0m
7.5.4
=== PowerShell Path ===
C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe
=== Antigravity Version ===
1.107.0
c19fdcaaf941f1ddd45860bfe2449ac40a3164c2
x64
1.18.4
In v1.19.4:
The tool falls back to legacy Windows PowerShell (powershell.exe, version 5.1).
> Write-Host "=== PowerShell Version ==="; Get-Host | Select-Object Version | Out-Host; Write-Host "=== PowerShell Path ==="; (Get-Process -Id $PID).Path | Out-Host; Write-Host "=== Antigravity Version ==="; Antigravity -v; (Get-Item "$(Split-Path (Get-Command Antigravity).Path)\..\Antigravity.exe").VersionInfo.FileVersion
=== PowerShell Version ===
Version
-------
5.1.19041.6456
=== PowerShell Path ===
C:\WINDOWS\SYSTEM32\WINDOWSPOWERSHELL\V1.0\powershell.exe
=== Antigravity Version ===
1.107.0
09171cd6214f9521f5202ffe72bda4443582da95
x64
1.19.4
For anyone who wants to avoid the popups, or simply prefers to keep using PowerShell 7 (pwsh) for their workflows, rolling back to v1.18.4 is a viable temporary workaround.
Important: Please remember to disable the auto-update feature in the settings before installing the older version, otherwise, it will automatically update back to v1.19.4.
Here is the direct download link for the previous installer:
https://edgedl.me.gvt1.com/edgedl/release2/j0qc3/antigravity/stable/1.18.4-5780041996042240/windows-x64/Antigravity.exe
2 Likes
@KevinHaHaHa you can’t rollback.. b/c when you do once you open up the agent manager it says your version out of date and forces you to get the latest version
You can still roll back. Go into the editor settings, then search for UPDATE MODE. Then, select the NONE option from the dropdown list.
After this, download the old stable version and install.
2 Likes
wow, thanks Bro.. this is very helpful. I thought I had no way out of the nighmare. I will now revert back to 1.18.4 until a more stable version is released. Thanks again.
1 Like
@NeoNerd @Ambrish_Chaurasiya you guys both have been so helpful I truly appreciate it, but currently I’m dealing with 3 issues that maybe you can provide some solutions for so I can be back on my way this morning.
Issue 1- Can’t revert bask to the 1.18 version which I feel is more stable for me at this juncture. I tried what you suggested @Ambrish_Chaurasiya however when i click on Antigravity Settings there is no search bar so i can search for UPDATE MODE and select this and restart so I can revert back. Am I missing something?
Issue 2 the dafault view for the IDE that I had when i first launched antigravity now I see this (screenshot provided) . There used to be a big blue button that said Open Eidtor, and some other things in the center and down on the left panel there were some menues there like browser, etc so how do i get back to this default view?
Issue 3- This is probably the main one. When I’m in the Agent Manager view which is really what I mainly work in and I go to some of my previous sessions when I click on some of those “sessions” under “Workspaces” some of them I go into have the history and some don’t . For the ones that don’t the Agent sits there and constantly Spins as if trying to find those chat histories but is unable to and immediately when I go to the Agent Manager view the PC fan goes into high processing mode for quite some time and i fear that I’m burning tokens b/c the agents are spinning trying to gather the chat history? This is why I’m wanting to revert back b/c in 1.18 this did NOT happen and I was able to get into all of my chat history. Even with the new update this morning this is STILL happening so they didn’t fix this part yet, meaning you can get to all of your chat history and until they do I desire not to update.
- Not an issue but a question. As I was playing around today trying to get my default panel view back in the initial IDE that opens up when I launch the Application, I call it “Editor” I somehow landed on an Extensions side panel and there were some recommend extenstions like Docker and PowerShell and Google Cloud Code etc.. but when i choose to install them a big “Trust” button appears with some language about being careful so my question is are these safe to install?
Thanks for you help. Personally I’d love it if I could just pick up the phone on some of this and call you guys as you seem more experienced with the IDE but I guess for now this works just as well. Thanks for your time.
@Ambrish_Chaurasiya @NeoNerd i was able to figure out issue number 2. thanks to Gemini. Also one thing this morning’s update did resolve was all of those 8 cmd popups from happening which i also know it was my MCP’s starting but Thanks to @NeoNerd i Had resloved at least 4 of them before i went to bed last night so with this release that is a non issue, however Issue 3 is my main issue with today’s release so this is why I still want to be able to revert back to 1.18 version for now. of course if I can do that then Issue 3 is also a non issue for me
Reverting to Antigravity v1.18.4
Hi — thanks for the update. Below are the steps to revert safely to version 1.18.4 and prevent automatic updates.
1. Open Settings
- Click the Settings (gear) icon in the top toolbar.
2. Open Editor Settings
- From the menu, select Editor Settings.
3. Disable Automatic Updates
- In the settings page, use the search bar.
- Search for:
UPDATE
or
UPDATE MODE
- Locate Update: Mode.
- Change the dropdown value to:
none
What this does
- Disables automatic updates.
- Prevents Antigravity from upgrading automatically.
- A restart may be required after changing this setting.
4. Install Version 1.18.4
- Go to the official Antigravity website.
- Download version 1.18.4.
- Install it normally.
Because Update Mode = none, the IDE will not auto-update to newer versions.
Current Status (Important Clarification)
- The session history issue still persists on version 1.18.4.
- Aside from that, everything else is working fine.
- I have not installed version 1.19.6 yet, so I cannot confirm whether:
- the chat session history issue, or
- the terminal pop-up problem
has been resolved in the latest release.
Summary
- Auto updates disabled
- Running v1.18.4
- Session history issue still present
- Version 1.19.6 not tested yet
If you decide to test version 1.19.6 later, sharing the results would help confirm whether those issues are fixed.
1 Like
@Ambrish_Chaurasiya Thanks. When i try to do this i get a warning (which I can’t share b/c of sensitive information) but what i can tell you is when i click on the blue “Open Settings” button that it takes me into a settings.json 8 file and bascially there are a bunch of Server path’s that are underlined in red (So far I have 8 MCP) servers and like one gsc-auditor-key.json (Google_Application_Credentials) file and about 7 index.js files related to mcp’s and or bridges may have something to do with these warnings, but all that’s over my head. So unfortunately b/c of that I can’t do this. But i notice you said even though you can revert back to 1.18.4 that you’re still having session history issues? Wow. I never had these issues in that version. I do now have 1.19.6 , however, i had to come up with a workaround and i mention what that was in a post that i titled “Fix if you lost your session history with the new upgrade per Antigravity” yesterday, if this helps? At this point that “workaround fix” helps me keep chat history going foward but I’ve basically lost all the rest of my chat history prior to the new chat conversations I’ve started moving foward so go figure. To me they need to just come up with an update that allows you go get all of your previous chat history @Abhijit_Pramanik So b/c of this that you’re informing me of, i might as well stay with 1.19.6 and hope that release a version that let’s you go back and get all your previous chat history.. Thanks for sharing.
Good news! It looks like the latest update (v1.19.6) has resolved the default shell issue. The background execution has successfully switched back to utilizing PowerShell Core (pwsh.exe).
Here are the logs confirming the fix:
> Write-Host "=== PowerShell Version ==="; Get-Host | Select-Object Version | Out-Host; Write-Host "=== PowerShell Path ==="; (Get-Process -Id $PID).Path | Out-Host; Write-Host "=== Antigravity Version ==="; Antigravity -v; (Get-Item "$(Split-Path (Get-Command Antigravity).Path)\..\Antigravity.exe").VersionInfo.FileVersion
=== PowerShell Version ===
e[32;1mVersione[0m
e[32;1m-------e[0m
7.5.4
=== PowerShell Path ===
C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe
=== Antigravity Version ===
1.107.0
d2597a5c475647ed306b22de1e39853c7812d07d
x64
1.19.6
For those who rolled back to v1.18.4, it should be safe to re-enable auto-updates and upgrade to the latest version now!
1 Like