[Bug] Antigravity keeps asking for browser sign-in despite successful CLI authentication on macOS

[lokize]

Description

I'm experiencing an authentication issue when trying to use Google Antigravity as an agent inside Orca IDE on macOS.

The Antigravity CLI (agy) is already installed and successfully authenticated with my Google account. It works correctly when executed directly from the terminal.

However, whenever I try to send a message using the Antigravity agent inside Orca IDE, the following error appears:

Your message was not sent.

Sign in to Antigravity. The agent asked to sign in in a browser

Environment

• Operating System: macOS
• Orca IDE version: 1.4.230
• Antigravity CLI version: 1.4.2
• CLI executable: ~/.local/bin/agy
• Agent: Antigravity
• Agent status: Enabled

Steps to Reproduce

1. Install the official Google Antigravity CLI.
2. Authenticate successfully with a Google account.
3. Verify that the CLI works in the terminal:

agy --version
agy -p "Reply only OK"

4. Open Orca IDE.
5. Enable the Antigravity agent.
6. Configure the agent command using agy or its absolute executable path.
7. Create a new Antigravity chat and send a message.

Actual Behavior

Orca refuses to send the message and displays:

Sign in to Antigravity. The agent asked to sign in in a browser

No successful authentication flow is presented in the chat.

Expected Behavior

Orca should recognize the existing authenticated Antigravity CLI session or provide a working browser authentication flow so the agent can be used normally.

Troubleshooting Already Performed

• Confirmed that agy is installed and accessible.
• Verified CLI version 1.4.2.
• Successfully executed agy -p "Reply only OK", which returned OK.
• Refreshed Antigravity accounts in Orca.
• Used the Save current account option.
• Confirmed that Antigravity usage limits are displayed in Orca.
• Restarted Orca IDE.
• Created new Antigravity chat sessions.
• Changed the agent command from agy to the absolute executable path.
• Removed --dangerously-skip-permissions for testing.

The issue persists.

Additional Information

Orca's Antigravity account settings mention that Antigravity chats run a separate server downloaded by Orca, independent of the agy CLI.

Could this be an authentication/session synchronization issue between the native Antigravity CLI and Orca's internal Antigravity server?

Is there an additional authentication step required for the internal server?

Any guidance or a fix would be appreciated.

[lokize]

with terminal cli its working but chat ui not

[AmethystLiang]

Turns out Antigravity ACP uses a different sign in token. @brennanb2025 is working on fixing this.

The fix will be out in our next release later today.