What happened?
Bug Report: /ide install error: " ✕ agy not found. Please ensure it is in your system's PATH. "
On IDE integration with Google's Antigravity: Gemini CLI fails to detect Antigravity IDE on non-Debian/Ubuntu Linux distributions due to binary naming mismatch.
Current Fix / Workaround: Users currently have to manually create a symbolic link to satisfy the CLI's detection logic: sudo ln -s /usr/bin/antigravity /usr/local/bin/agy.
The Gemini CLI (specifically within the @google/gemini-cli-core logic) fails to detect a valid Antigravity IDE installation on several Linux distributions. While the CLI expects a binary named agy, many package managers (or official installers on these distros) install the binary as antigravity in /usr/bin/. Consequently, running the /ide install command results in the error: ✕ agy not found. Please ensure it is in your system's PATH.
Root Cause Analysis: The detection logic in the editor utility (specifically in @google/gemini-cli-core/dist/src/utils/editor.js) appears to have a hardcoded mapping for the Antigravity command. Currently, it is likely configured as: antigravity: { win32: ['agy.cmd'], default: ['agy'] }.
On some Linux distributions, the system provides /usr/bin/antigravity, but no agy alias is created by default. This causes the CLI to report the IDE as "(Not installed)".
Steps to Reproduce:
-
Install Antigravity on a non-Ubuntu Linux distribution (e.g., Arch Linux).
-
Verify the binary exists via which antigravity (typically returns /usr/bin/antigravity).
-
Run gemini and attempt to use /ide install or check /ide status.
-
Observe that Antigravity is not detected because the CLI is strictly looking for the agy command.
Expected Behavior:
The Gemini CLI should check for both agy and antigravity as valid command names for the IDE on Linux systems.
Suggested Fix:
Update the editorCommands mapping in the CLI core to include antigravity as a fallback for the default (non-Windows) platform: antigravity: { win32: ['agy.cmd'], default: ['agy', 'antigravity'] }.
Current Workaround:
Users currently have to manually create a symbolic link to satisfy the CLI's detection logic: sudo ln -s /usr/bin/antigravity /usr/local/bin/agy.
Environment:
Gemini CLI Version: [Vul hier je versie in, bijv. 0.22.2]
OS: Linux (Non-Debian/Ubuntu)
IDE: Google Antigravity
What did you expect to happen?
Expected Behavior:
The Gemini CLI should check for both agy and antigravity as valid command names for the IDE on Linux systems.
Client information
- CLI Version: 0.21.3
- Git Commit: d0cdeda
- Session ID: f287d90d-a323-49c5-ab22-365eeebe5489
- Operating System: linux v22.20.0
- Sandbox Environment: no sandbox
- Model Version: auto-gemini-3
- Memory Usage: 225.9 MB
- IDE Client: Antigravity
Login information
Google Account
Anything else we need to know?
Current Workaround:
Users currently have to manually create a symbolic link to satisfy the CLI's detection logic: sudo ln -s /usr/bin/antigravity /usr/local/bin/agy.
Suggested Fix:
Update the editorCommands mapping in the CLI core to include antigravity as a fallback for the default (non-Windows) platform: antigravity: { win32: ['agy.cmd'], default: ['agy', 'antigravity'] }.
What happened?
Bug Report: /ide install error: " ✕ agy not found. Please ensure it is in your system's PATH. "
On IDE integration with Google's Antigravity: Gemini CLI fails to detect Antigravity IDE on non-Debian/Ubuntu Linux distributions due to binary naming mismatch.
Current Fix / Workaround: Users currently have to manually create a symbolic link to satisfy the CLI's detection logic: sudo ln -s /usr/bin/antigravity /usr/local/bin/agy.
The Gemini CLI (specifically within the @google/gemini-cli-core logic) fails to detect a valid Antigravity IDE installation on several Linux distributions. While the CLI expects a binary named agy, many package managers (or official installers on these distros) install the binary as antigravity in /usr/bin/. Consequently, running the /ide install command results in the error: ✕ agy not found. Please ensure it is in your system's PATH.
Root Cause Analysis: The detection logic in the editor utility (specifically in @google/gemini-cli-core/dist/src/utils/editor.js) appears to have a hardcoded mapping for the Antigravity command. Currently, it is likely configured as: antigravity: { win32: ['agy.cmd'], default: ['agy'] }.
On some Linux distributions, the system provides /usr/bin/antigravity, but no agy alias is created by default. This causes the CLI to report the IDE as "(Not installed)".
Steps to Reproduce:
Install Antigravity on a non-Ubuntu Linux distribution (e.g., Arch Linux).
Verify the binary exists via which antigravity (typically returns /usr/bin/antigravity).
Run gemini and attempt to use /ide install or check /ide status.
Observe that Antigravity is not detected because the CLI is strictly looking for the agy command.
Expected Behavior:
The Gemini CLI should check for both agy and antigravity as valid command names for the IDE on Linux systems.
Suggested Fix:
Update the editorCommands mapping in the CLI core to include antigravity as a fallback for the default (non-Windows) platform: antigravity: { win32: ['agy.cmd'], default: ['agy', 'antigravity'] }.
Current Workaround:
Users currently have to manually create a symbolic link to satisfy the CLI's detection logic: sudo ln -s /usr/bin/antigravity /usr/local/bin/agy.
Environment:
Gemini CLI Version: [Vul hier je versie in, bijv. 0.22.2]
OS: Linux (Non-Debian/Ubuntu)
IDE: Google Antigravity
What did you expect to happen?
Expected Behavior:
The Gemini CLI should check for both agy and antigravity as valid command names for the IDE on Linux systems.
Client information
Login information
Google Account
Anything else we need to know?
Current Workaround:
Users currently have to manually create a symbolic link to satisfy the CLI's detection logic: sudo ln -s /usr/bin/antigravity /usr/local/bin/agy.
Suggested Fix:
Update the editorCommands mapping in the CLI core to include antigravity as a fallback for the default (non-Windows) platform: antigravity: { win32: ['agy.cmd'], default: ['agy', 'antigravity'] }.