Synara connects to Google’s Antigravity CLI through the agy executable. Antigravity owns its account session, models, permissions, tools, and conversation runtime; Synara supplies the task boundary, working environment, transcript, browser, terminal, diff, and Git workflow around it.

Install

On macOS and Linux, use the official installer:

curl -fsSL https://antigravity.google/cli/install.sh | bash

On Windows PowerShell:

irm https://antigravity.google/cli/install.ps1 | iex

The Unix installer normally places agy under ~/.local/bin. Verify the executable from a fresh terminal:

agy --version

Authenticate

Start Antigravity in a normal terminal:

agy

Antigravity first checks the operating system’s secure keyring. If no valid session exists, it opens Google Sign-In in a browser. In an SSH or remote session, it can print an authorization URL and accept the resulting code in the terminal.

To remove stored credentials from an interactive Antigravity session, use:

/logout

Synara does not copy or replace the credential profile stored by Antigravity.

Verify

From a clean test directory:

mkdir -p /tmp/agy-synara-check
cd /tmp/agy-synara-check
agy

Confirm that Antigravity starts without a keyring or sign-in error and can answer a harmless read-only request. Exit before making changes. This isolates installation and authentication problems from Synara.

Connect to Synara

Enable Antigravity

Open provider settings and confirm that Synara detects agy.

Check the executable path

Use automatic discovery unless you intentionally installed Antigravity elsewhere. A custom binary path must point to the executable itself.

Refresh models

Confirm that Synara can discover the models exposed by the installed Antigravity runtime.

Start a bounded task

Use a clean repository and a small objective. Review the selected model, mode, and working environment before sending the first turn.

Capabilities in Synara

Antigravity sessions can expose:

Model selection discovered from the installed runtime
Assistant output, command execution, file changes, and web-search activity
Permission requests surfaced through Synara
Plan-oriented and normal task workflows supported by the runtime
Attachments projected into the provider prompt
Conversation continuity where the runtime supplies a conversation identifier
Synara’s terminal, browser, diff, checkpoint, and Git delivery surfaces

Synara does not currently classify Antigravity as supporting native live-turn steering. Use interruption and follow-up controls according to the state shown in the active task.

Antigravity keeps its own settings and conversation data. Changes to its permission mode, sandbox, model, hooks, or workspace trust can alter behavior even when the same task is opened through Synara.

Updating

Antigravity includes a native update path and its installer can install or upgrade the CLI. Keep the installation directory writable by your user and restart Synara after the executable changes.

If an update is stuck, check Antigravity’s own updater status and lock files before reinstalling. Do not delete unrelated files from its configuration directory.

Troubleshooting

Antigravity is not detected

Run agy --version from a fresh terminal.
Confirm ~/.local/bin or the Windows installation directory is on PATH.
Remove or correct an obsolete custom binary path in Synara.
Restart Synara after installation or shell-profile changes.

Antigravity