Background
When attempting to use Google’s new antigravity-cli (command agy), users with older server CPUs (like the J1900) that do not support the AES-NI hardware instruction set will encounter an immediate crash:
| |
Based on online research, this occurs because the Antigravity CLI is written in Go and compiled with a high microarchitecture level requirement (such as GOAMD64=v3), which strictly requires physical AES support. The application fails fast before any configurations can be loaded.
Drawing from previous experience fixing a similar crash with the Antigravity IDE, we can utilize the Intel® Software Development Emulator (SDE) to intercept and simulate the AES instruction set, allowing the CLI to run normally.
Solution
The following steps outline the workaround. Please note that because the instructions are being simulated via software, the execution and response times of the agy command will be slower than usual.
1. Prepare Intel SDE
If you have already installed SDE to fix the IDE issue, you can skip this step.
Download the latest Linux archive from the Intel® Software Development Emulator page.
| |
2. Allow Process Injection
Intel SDE relies on ptrace to hijack the binary. Ensure your Debian system allows this:
| |
3. Hijack and Replace the agy Binary
First, locate where agy is installed:
| |
Rename the original executable to hide it and serve as a backup:
| |
Create a new interception wrapper script in its place:
| |
Paste the following script (ensure the SDE_BIN path matches your actual path):
| |
Grant execute permissions to the wrapper script:
| |
Testing and Rollback Strategy
Test the CLI
Run the following command in your terminal:
| |
If it successfully outputs the version number without throwing an Illegal instruction error, the workaround was successful.
🚨 Quick Rollback
If this solution causes system instability or you wish to revert to the original state, run the following commands to restore the backed-up file:
| |