Antigravity gets a Linux Chinese-localization build: check compatibility before running it

Antigravity gets a Linux Chinese-localization build: check compatibility before running it

Linux users looking for a Chinese Antigravity interface now have a community build to download. An Antigravity-Hans fork published a Linux release tagged v0.4.10 on November 14, 2026.

Match the binary and the application separately

The asset list contains amd64 and arm64 Linux executables, each with a checksum. Pick the file for your processor architecture rather than a source archive. A matching checksum helps verify the downloaded file; it does not establish that the program will work correctly.

Keep the version numbers separate, too. v0.4.10 identifies this localization-tool release. The upstream README names Antigravity 2.31.0 and Antigravity IDE 2.6.0 as its adaptation targets.

The fork's README still concentrates on Windows and macOS launch instructions. Its release note adds no Linux installation procedure, distribution list or compatibility results. Those materials do not establish Linux compatibility, and the upstream adaptation targets should not be extended to every newer application release.

A live translation layer is not an installation patch

Upstream recommends its dynamic mode, which translates the interface through CDP while preserving installed application resources. The injected state disappears when the application page closes. Its alternative static mode is limited to the IDE and modifies local installation resources, including checksum repair. Those approaches require different expectations about reverting changes.

They also cover different surfaces. Upstream says the regular application's Swarm panel, plus the IDE's agent and standalone settings pages, need the dynamic monitor. A static patch does not cover those embedded pages. A translated main window is therefore not a complete acceptance test.

Our recommendation is to test outside important work and check permission menus, settings and the editing area separately. Because dynamic translation leaves installed resources intact, it is the sensible approach to ask the maintainer about first.

Exiting the launcher, stopping the background monitor and clearing the page injection are separate actions. The README documents antigravity-hans --stop for ending localization monitors started by the tool; injected state disappears when the application page closes. Do not assume that exiting the launcher completes cleanup. Save unfinished work before testing and ask the maintainer to confirm how this stopping mechanism behaves on Linux: the mechanism is documented, but Linux validation results are not. Reversing a static patch requires the patch restoration function, not a monitor-stop command.

Share this article