gemini-cli - 💡(How to fix) Fix Compatibility Issue: Antigravity CLI requires AVX instructions missing on legacy CPUs (AMD A-Series)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

I am a Google AI Pro user. The primary reason for my subscription is the Gemini CLI, which currently works perfectly on my hardware. I am being notified to migrate to the new Antigravity CLI, but the current linux_amd64 binary fails immediately with an "Illegal instruction" error (Exit Code 132).

RAW_BUFFERClick to expand / collapse

What happened?

I am a Google AI Pro user. The primary reason for my subscription is the Gemini CLI, which currently works perfectly on my hardware. I am being notified to migrate to the new Antigravity CLI, but the current linux_amd64 binary fails immediately with an "Illegal instruction" error (Exit Code 132). My system runs on an AMD A6-3420M APU. This is a legacy processor that does not support AVX/AVX2 instruction sets. It appears the new Antigravity CLI binary was compiled requiring these modern instructions as a baseline.

What did you expect to happen?

I expected the new Antigravity CLI to run on my system, or for there to be a "baseline" x86_64-v1 binary available that does not require AVX. Since I pay for Google AI Pro specifically for CLI access, the forced migration on June 18th will make my subscription obsolete for my current setup if a compatible build isn't provided.

Client information

  • CLI Version: 0.42.0
  • Git Commit: 68e2196d5
  • Session ID: d71251b3-0961-4257-9390-f17e1fc05bac
  • Operating System: linux v24.14.1
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 360.3 MB
  • Terminal Name: Konsole 26.04.1
  • Terminal Background: #232627
  • Kitty Keyboard Protocol: Unsupported

Login information

Signed in with Google Account (oauth-personal) / Google One AI Pro Tier.

Anything else we need to know?

While the Node.js-based Gemini CLI works flawlessly on this machine, the new Go-based Antigravity CLI is physically incompatible with my CPU due to the AVX requirement. Please provide a baseline x86_64-v1 binary so users with stable legacy hardware can continue using the service they pay for.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

gemini-cli - 💡(How to fix) Fix Compatibility Issue: Antigravity CLI requires AVX instructions missing on legacy CPUs (AMD A-Series)