Package Details: antigravity 1.23.2-1

Git Clone URL: https://aur.archlinux.org/antigravity.git (read-only, click to copy)
Package Base: antigravity
Description: An agentic development platform from Google, evolving the IDE into the agent-first era.
Upstream URL: https://antigravity.google/
Keywords: ai-coding ai-ide antigravity editor google ide vibe-coding vscode vscode-fork
Licenses: LicenseRef-Google-Antigravity
Submitter: Doshiba
Maintainer: HurricanePootis (AlphaLynx)
Last Packager: HurricanePootis
Votes: 68
Popularity: 16.45
First Submitted: 2025-11-18 18:05 (UTC)
Last Updated: 2026-04-16 21:23 (UTC)

Pinned Comments

w568w commented on 2025-12-20 09:19 (UTC) (edited on 2025-12-20 09:23 (UTC) by w568w)

I wrote this launch script to disable core dumps and clean up lingering processes on exit: https://gist.github.com/w568w/0999f61e9a646feac3f5a46aaa17e1d1

Leverages systemd scopes for process tracking to prevent collateral killing when multiple antigravity instances are active.

Confirmed the high CPU and leftover process issues are fixed.

Latest Comments

1 2 3 4 5 6 .. 12 Next › Last »

muhammed_mahmoud commented on 2026-04-09 21:28 (UTC)

The last time i installed Antigravity it had a problem that took almost my entire disk space is it fixed or not?

spundun commented on 2026-04-03 17:32 (UTC) (edited on 2026-04-03 17:33 (UTC) by spundun)

I installed antigravity, opened, flipped through initial setup to get to the "Sign in with Google" button, I click that button but nothing happens!

Has anyone else experienced this? What's the solution? I have firefox browser installed.

AlphaLynx commented on 2026-04-03 00:42 (UTC) (edited on 2026-04-03 00:47 (UTC) by AlphaLynx)

The electron package guidelines say to use /opt if it contains prebuilt electron. And switching to FHS location wouldn't fix serve-web, the error is spawn /opt/Antigravity/bin/antigravity-tunnel ENOENT, so if that binary existed it would work (in theory). I get the same error on Debian following the official upstream installation guide, so this is a binary not provided by upstream in the first place. The same error occurs when building Code-OSS from source (microsoft/vscode#221346, closed with "as-designed"), and in other forks like VSCodium and Cursor. That binary is a proprietary part of official VS Code so the command won't work on any forks.

Lime commented on 2026-04-02 19:14 (UTC)

Can this be updated to place files in their FHS locations? Right now they're all lumped into /opt, so commands like antigravity serve-web are broken.

AlphaLynx commented on 2026-03-25 02:43 (UTC)

flags script added 🙂

jobeto86 commented on 2026-03-24 19:34 (UTC)

Comentario:

Add wrapper script for user-configurable flags (à la visual-studio-code-bin)

Currently /usr/bin/antigravity is a symlink to /opt/Antigravity/bin/antigravity, which means users have no way to persistently pass Electron/Chromium flags like --ozone-platform=wayland or --disable-gpu.

This adds a antigravity.sh wrapper (same pattern as visual-studio-code-bin) that reads flags from ~/.config/antigravity-flags.conf and passes them to the real binary.

Changes:

New file antigravity.sh:

!/bin/bash
Allow users to override command-line options

XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-$HOME/.config}" ANTIGRAVITY_FLAGS_FILE="${XDG_CONFIG_HOME}/antigravity-flags.conf"

declare -a flags

if [[ -f "${ANTIGRAVITY_FLAGS_FILE}" ]]; then while IFS= read -r line || [[ -n "${line}" ]]; do # Skip comments and empty lines if [[ ! "${line}" =~ ^[[:space:]]*# ]] && [[ -n "${line}" ]]; then flags+=("${line}") fi done < "${ANTIGRAVITY_FLAGS_FILE}" fi

exec /opt/Antigravity/bin/antigravity "${flags[@]}" "$@" PKGBUILD diff:

+source=("$pkgname.sh") +sha256sums=('SKIP')

moetayuko commented on 2026-03-24 11:04 (UTC)

please add a wrapper script for passing user flags, similar to https://aur.archlinux.org/cgit/aur.git/tree/visual-studio-code-bin.sh?h=visual-studio-code-bin

jobeto86 commented on 2026-03-17 01:24 (UTC)

To answer your question: my PR only addresses the glibc 2.43 SYS_SECCOMP collision with the Chromium sandbox headers and adds ThinLTO — it does not touch anything related to native Node modules or V8 ABI compatibility.

To be honest, I wasn't aware of the native module breakage issue you described. My use case is fairly limited: I mainly use Antigravity for TypeScript/Java development with extensions like Claude Code, the Spring Boot/Java pack, Vue (Volar), Python, Docker, and a bunch of themes/icon packs, nothing that exercises heavy native bindings like @parcel/watcher. Guess I was lucky not to run into it.

Your decision to bundle Electron makes complete sense given that context. Thanks for the explanation. I look forward to providing electron40 -v3 or electron41 -v3 whatever version Antigravity jumps to.

jobeto86 commented on 2026-03-17 00:33 (UTC)

By the way, we opened a PR to CachyOS-PKGBUILDS adding electron39 with the glibc 2.43 fix and ThinLTO (#1224). If it gets merged, CachyOS users would have a system electron39 available in cachyos-extra-v3. Just mentioning in case it's useful context. Thanks again for the explanation!

jobeto86 commented on 2026-03-17 00:14 (UTC) (edited on 2026-03-17 00:15 (UTC) by jobeto86)

Fair point, you're right that the glibc 2.43 fix in #1224 is unrelated to the native module breakage. I was conflating two separate issues. Bundled makes sense for Antigravity's case.

Thanks for taking the time to explain! ;)

1 2 3 4 5 6 .. 12 Next › Last »