Connect Antigravity to Other AI Coding Agents

acc install --adapter antigravity

Follow the installer instructions and start a fresh CLI session with an open project workspace. ACC's captured CLI hooks provide context before a model invocation; a session without an open workspace can register nothing.

Experimental live delivery uses a relay the agent starts from its own shell. That shell holds the session endpoint unavailable to ordinary hook processes. The installed instructions explain the relay, and current setup can allow ACC commands under the client's approval rules. Windows has its own relay transport and permission-prompt behavior.

The CLI evidence starts at 1.2.7. Print mode and the first session in a folder trusted during that launch have documented relay limitations. Use the actual receiving mode reported for your session.

The desktop app runs hooks through its language server. The captured desktop 2.19.1 live path uses that server directly, so the agent does not start the CLI relay.

A reopened conversation becomes reachable again from its next turn after the app restarts. Desktop installation and command grants also have their own requirements. The current integration setup still uses Antigravity CLI to read hook registration back.

CLI support alone is therefore insufficient evidence for a desktop claim.

Open Antigravity and the other client independently in the same ACC workspace. Activate the Claude Code or Codex integration as appropriate, then follow the cross-client connection guide.

This workflow exchanges messages between coding sessions. It does not configure Claude as a model inside Antigravity or share provider credentials.

For an Antigravity interface session:

Build the registration form. Ask the service session through ACC for the request, response, and validation-error contract. Return any interface requirement that changes that contract.

Have the service session answer in the same thread. These are example instructions, not a recorded product run.

ACC does not give Antigravity a certified tool write guard. Agree on editing boundaries even when another client's claims can be guarded.

Use separate worktrees for separate checkouts, and read delivery behavior before expecting an idle session to act. The compatibility matrix keeps CLI and desktop evidence visible.