Environment
- SDK version: 0.1.6 (latest on PyPI)
- CLI version: 1.1.0
- Target OS/platform: Intel macOS (
x86_64 / darwin_amd64)
- Install method:
python3 -m pip install google-antigravity
Description
The official Antigravity CLI supports Intel Macs, but the Python SDK does not currently publish a compatible macOS package.
The CLI installer explicitly maps:
x86_64|amd64) arch="amd64"
and the live darwin_amd64 release manifest currently publishes CLI 1.1.0 as:
.../darwin-x64/cli_mac_x64.tar.gz
The executable in that archive is a Mach-O 64-bit x86_64 binary.
In comparison, the complete PyPI file list for google-antigravity==0.1.6 contains:
google_antigravity-0.1.6-py3-none-macosx_11_0_arm64.whl
google_antigravity-0.1.6-py3-none-manylinux_2_17_aarch64.whl
google_antigravity-0.1.6-py3-none-manylinux_2_17_x86_64.whl
google_antigravity-0.1.6-py3-none-win_amd64.whl
google_antigravity-0.1.6-py3-none-win_arm64.whl
There is no macOS x86_64 wheel, Universal2 wheel, or source distribution. Since the wheel bundles the native localharness, an Intel Mac cannot fall back to a portable Python-only installation.
Expected Behavior
The SDK should support the same macOS architectures supported by the CLI.
Please publish either:
- a
macosx_11_0_x86_64 wheel containing an x86_64 localharness, or
- a Universal2 macOS wheel containing an
arm64 + x86_64 localharness.
Actual Behavior
Only Apple Silicon has a macOS SDK wheel, even though the official CLI has both Apple Silicon and Intel release paths.
Why this matters
Applications integrating Antigravity should be able to provide a consistent experience across every desktop platform supported by agy. Requiring an application to retain a separate CLI-only implementation specifically for Intel Mac users makes SDK migration and provider behavior inconsistent.
Verification commands
CLI architecture detection:
curl -fsSL https://antigravity.google/cli/install.sh
CLI Intel release manifest:
curl -fsSL https://antigravity-cli-auto-updater-974169037036.us-central1.run.app/manifests/darwin_amd64.json
SDK package artifacts:
curl -fsSL https://pypi.org/pypi/google-antigravity/0.1.6/json |
jq -r '.urls[].filename'
This report is based on inspecting the official installer, live release manifest, downloaded CLI artifact, and PyPI package list. I do not currently have an Intel Mac available for an on-device runtime reproduction.
Environment
x86_64/darwin_amd64)python3 -m pip install google-antigravityDescription
The official Antigravity CLI supports Intel Macs, but the Python SDK does not currently publish a compatible macOS package.
The CLI installer explicitly maps:
and the live
darwin_amd64release manifest currently publishes CLI 1.1.0 as:The executable in that archive is a Mach-O 64-bit
x86_64binary.In comparison, the complete PyPI file list for
google-antigravity==0.1.6contains:There is no macOS x86_64 wheel, Universal2 wheel, or source distribution. Since the wheel bundles the native
localharness, an Intel Mac cannot fall back to a portable Python-only installation.Expected Behavior
The SDK should support the same macOS architectures supported by the CLI.
Please publish either:
macosx_11_0_x86_64wheel containing an x86_64localharness, orarm64+x86_64localharness.Actual Behavior
Only Apple Silicon has a macOS SDK wheel, even though the official CLI has both Apple Silicon and Intel release paths.
Why this matters
Applications integrating Antigravity should be able to provide a consistent experience across every desktop platform supported by
agy. Requiring an application to retain a separate CLI-only implementation specifically for Intel Mac users makes SDK migration and provider behavior inconsistent.Verification commands
CLI architecture detection:
CLI Intel release manifest:
SDK package artifacts:
This report is based on inspecting the official installer, live release manifest, downloaded CLI artifact, and PyPI package list. I do not currently have an Intel Mac available for an on-device runtime reproduction.