When attempting to install the Antigravity CLI on a machine with an older but highly capable processor (Intel Xeon circa 2011), the installation script crashes with an Illegal instruction (core dumped) error.
The error log indicates a go/sigill-fail-fast panic because the binary was compiled requiring hardware AES instructions (aes enabled), which are not available on this specific CPU architecture. Many of these older processors are still extremely fast, reliable, and widely used in home labs and legacy server deployments, making them perfectly valid environments for this tool if not for this strict compilation flag.
Steps to reproduce the behavior:
Attempt to run the installation script on a Linux system with a legacy CPU lacking AES-NI instruction support (e.g., specific older Intel Xeon models).
The script downloads the binary and attempts to execute it.
The process immediately crashes during execution.
The CLI should ideally have a software fallback for cryptographic operations if hardware AES is not detected, allowing it to run on older x86_64 processors. Alternatively, offering a separate "legacy" build compiled without the strict AES requirement (GOAMD64=v1) would allow the tool to remain accessible for users maintaining older infrastructure.
Entorno (Environment)
OS: Linux (x86_64)
Hardware: Intel Xeon (2011 era)
CLI Version: 1.0.4
Logs / Error Output
Bash
⠋ Detecting system environment...
✓ Platform detected: linux_amd64
⠋ Querying release repository...
✓ Latest available version: 1.0.4
⠋ Downloading release package...
✓ Download complete and checksum verified.
⠋ Extracting binary from archive...
⠋ Configuring shell environment...
FATAL ERROR: This binary was compiled with aes enabled, but this feature is not available on this processor (go/sigill-fail-fast).
bash: línea 237: 7937 Instrucción ilegal ('core' generado) "$BINARY_PATH" install
When attempting to install the Antigravity CLI on a machine with an older but highly capable processor (Intel Xeon circa 2011), the installation script crashes with an Illegal instruction (core dumped) error.
The error log indicates a go/sigill-fail-fast panic because the binary was compiled requiring hardware AES instructions (aes enabled), which are not available on this specific CPU architecture. Many of these older processors are still extremely fast, reliable, and widely used in home labs and legacy server deployments, making them perfectly valid environments for this tool if not for this strict compilation flag.
Steps to reproduce the behavior:
Attempt to run the installation script on a Linux system with a legacy CPU lacking AES-NI instruction support (e.g., specific older Intel Xeon models).
The script downloads the binary and attempts to execute it.
The process immediately crashes during execution.
The CLI should ideally have a software fallback for cryptographic operations if hardware AES is not detected, allowing it to run on older x86_64 processors. Alternatively, offering a separate "legacy" build compiled without the strict AES requirement (GOAMD64=v1) would allow the tool to remain accessible for users maintaining older infrastructure.
Entorno (Environment)
OS: Linux (x86_64)
Hardware: Intel Xeon (2011 era)
CLI Version: 1.0.4
Logs / Error Output
Bash
⠋ Detecting system environment...
✓ Platform detected: linux_amd64
⠋ Querying release repository...
✓ Latest available version: 1.0.4
⠋ Downloading release package...
✓ Download complete and checksum verified.
⠋ Extracting binary from archive...
⠋ Configuring shell environment...
FATAL ERROR: This binary was compiled with aes enabled, but this feature is not available on this processor (go/sigill-fail-fast).
bash: línea 237: 7937 Instrucción ilegal ('core' generado) "$BINARY_PATH" install