Antigravity breaks Discord and system permissions. I am sick of fixing this broken IDE instead of working

Google Antigravity
1

I am absolutely losing my mind here. I just freshly formatted my PC after Google I/O to start clean, and I’m already wasting hours fixing stupid bugs. Out of nowhere, other apps like Discord started crashing immediately upon launch. After wasting hours digging through Event Viewers, reinstalling and reading crash logs, I found the absolute ridiculous root cause was Antigravity.

Why on earth is this IDE injecting an AppContainer ACL entry directly into %LOCALAPPDATA%\Programs and messing up the entire directory’s permissions? Because of this stupid inherited ACL sandbox restriction, every Chromium/Electron-based app (like Discord) fails to initialize its GPU sandbox, resulting in an immediate 0x80000003 APPCRASH.

I am incredibly frustrated. I installed an IDE to get my actual work done, not to spend my valuable time diagnosing broken system-level directory permissions that it broke without my permission! We’ve been dealing with a broken terminal, buggy UI, and pathetic quota, 429 errors… for months with zero improvement. Now, your tool is actively breaking system-level permissions.

Is the team actually going to fix how Antigravity handles ACLs, or are we seriously expected to manually append --disable-gpu-sandbox to every single shortcuts just to live with your broken architecture?

2

I already lost my mind over this. After playing around with antigravity-cli/antigravity I also ran into the same problem where discord, and other electron apps failed to load due to this exact issue.

VSCode was fine, but Discord and Termius stopped opening/working.

I’ll cut to the chase, I never was able to figure out how to fix this issue myself. I gave up, wiped my whole machine to Ubuntu “as the solution”.

This combined with a few other core experience issues with the antigravity-cli, like always needing to log in into every instance, and not being able to exit the process leaves me the impression the actual user experience/QA is just not there. I even would lean toward it was mostly vibe coded with minimal oversight due to these sorts of issues.

I’m still not clear if it was the CLI, or the IDE or the new “agent UI” as I installed all three at the same time, but I mostly only used the CLI. Either way I’m avoiding these tools for a while as I try to rebuild up my laptop.

3

They removed my post of how their team is handling so badly on the project like … because they feels it’s offensive :3. I mean like, they released a new agentic app as an update of AG which was IDE. Even so, that new agentic app is lacking a lot of features it should have and they don’t even bother to fix the problems like, Project title grouping for chat histories, losing chat histories after a crash or power outage, etc… And I even start found a lot of more broken stuff in their new apps after I force myself to continuously use their broken app.

4

they did 0 beta testing of this app. They said it at I/O event, all their projects are maximum 120 days timeline, they are vibe coding every piece of software that they release, but AI is not good enough yet, and therefore it’s all full of bugs and random AI slop. Anyone that tries using antigravity will for sure end up seeing some bugs, it’s essentially inevitable with how they made this app, which is just a rushed unfinished untested product

5

Thought I’d post my fix here, considering I just had this happen for the second time with the latest update. Here’s a powershell script that might help someone else out

#Requires -RunAsAdministrator

$paths = @($env:LOCALAPPDATA, $env:APPDATA, "C:\Program Files")
$removed = 0

foreach ($path in $paths) {
    Write-Host "Scanning: $path"
    $acl = Get-Acl $path

    $rules = $acl.Access | Where-Object {
        $_.IsInherited -eq $false -and
        $_.IdentityReference.Value -like "S-1-15-2-*"
    }

    if ($rules.Count -eq 0) {
        Write-Host "  No rogue AppContainer entries found."
        continue
    }

    foreach ($rule in $rules) {
        Write-Host "  Removing: $($rule.IdentityReference.Value) | $($rule.FileSystemRights)"
        $acl.RemoveAccessRule($rule) | Out-Null
        $removed++
    }

    Set-Acl $path $acl
    Write-Host "  Done."
}

Write-Host ""
Write-Host "Verifying..."
$allClean = $true
foreach ($path in $paths) {
    $acl = Get-Acl $path
    $match = $acl.Access | Where-Object {
        $_.IsInherited -eq $false -and
        $_.IdentityReference.Value -like "S-1-15-2-*"
    }
    if ($match) {
        Write-Host "STILL PRESENT at: $path"
        $allClean = $false
    } else {
        Write-Host "CLEAN: $path"
    }
}

Write-Host ""
if ($allClean -and $removed -gt 0) {
    Write-Host "Fixed! Removed $removed rogue AppContainer ACE(s). Restart any affected apps (Discord, Opera, etc)."
} elseif ($removed -eq 0) {
    Write-Host "Nothing to fix - no rogue AppContainer entries were found. Are you already clean?"
} else {
    Write-Host "Something may still be wrong. Try running as Administrator if you haven't."
}