Antigravity on macOS functionality?

[st0w]

Hello -

Wondering if I'm doing something wrong, or if support for Antigravity on macOS isn't ready yet, or something has changed in recent versions of the agy CLI that are complicating things. I've tried a few different ways, and can't get things working.

I installed 0.3.0 with the antigravity option, ran omni setup and then entered the Gemini API key I'd setup associated with a business plan. When I selected Antigravity and submitted a query (even "hello"), then switched to the Terminal tab, Antigravity would prompt me to login every single time - even though running agy from a shell worked and recognized my saved credentials. It also always asked me for my theme choice and to accept the TOS after every successful login.

After completing the login, Omni would send my query to agy, and I could see the response from it on the Terminal tab, but the web UI didn't seem to pick up on it and it would sit there showing Working... If I sent subsequent queries, they would get passed to agy and it would respond in the terminal - but again, no response would be shown in the web Chat window and it just sits there saying Working...

I tried running omni antigravity from the CLI. It would also start up Antigravity, but every time it was prompting me to login (despite having credentials in my keychain, and putting a creds JSON file where it needed to be).

I thought it might be related to issue #1477 and saw #1493 and #1585 , so I pulled down the latest main branch and built/installed that into a venv. It gets further now, but still doesn't seem to work. I also saw the antigravity-native-rpc-core-plan.md and antigravity-native-rpc-core-design.md documents, so wondering if things are in mid-change.

Now with the latest build from main, I start omni, start a new session, select Antigravity, and submit a query. When I switch over to the Terminal tab in the web UI, I see that it has started Antigravity with my saved credentials and is already logged in. But every time Antigravity starts, it is prompting for the terminal theme, and for me to accept the TOS.

Then it completes, and it appears to send the query to the agy CLI, but it always returns Agent execution terminated due to error. and the web UI chat just sits there showing Working... and never completes.

[st0w]

A bit more debugging.. I decided to modify _AGY_SEED_FILES in omnigent/antigravity_native_bridge.py to try to force including a theme into the config files that get copied into the bridge directory. I'd hoped this would bypass the selection at startup.

It didn't, and it still prompted me to select a theme. But then, the interaction from Omnigent chat actually worked and I got the response, rather than an error. I looked at agy-home/.gemini/antigravity-cli/settings.json in the bridge directory for that session. The theme was missing, but it did appear to use most of my /.gemini/antigravity-cli/settings.json file - including, notably, this section:

{
  "gcp": {
    "project": "business-project-name",
    "location": "us"
  }
}

This seems to be the key, since I'm using Antigravity logged in to an enterprise/business account, with a specific project selected. If I remove the "project" line from the settings JSON, it reverts back to the Agent execution terminated due to error. If I restore that line, it works again.

Seems this issue might be specific to people using Antigravity with a business account linked to a project?

[VectorPeak]

You’re not doing anything obviously wrong here. The screenshots show two separate layers behaving differently: Omni is successfully starting agy and sending turns into the terminal, and Antigravity is responding there; the broken part is the bridge back into the web chat, which is why the Chat tab stays on Working... while the Terminal tab has the actual answer.

The repeated login/theme/TOS behavior looks like agy is being launched by Omni in an environment that does not fully reuse the same first-run state as your normal shell. On main, that seems improved for auth in your second screenshot - it starts logged in and reaches the Antigravity prompt - but the third screenshot still shows the color-scheme onboarding screen, so the persisted Antigravity config is still not being applied consistently.

The RPC docs you found are relevant: the current native Antigravity integration is in the middle of moving away from terminal/transcript tailing toward Antigravity’s structured RPC surface. The design doc explicitly calls out the exact class of issue you’re seeing: terminal output exists, but the web UI does not reliably receive committed trajectory steps because the old read path depends on mirroring Antigravity’s transcript/log behavior.

One correction to the _AGY_SEED_FILES direction: seeding theme/config files may paper over the onboarding prompt, but it won’t fix the Working... chat issue by itself. That symptom is on the read/forwarding side, not the send side. The fact that what's your name is answered in the terminal while the chat remains pending is a good repro for that.

Useful repro details to include in the issue would be:

macOS version
omnigent version / commit SHA
agy version
output of: which agy
output of: agy --version

---
If my answer solved your problem, you can click **answered the question**. I'm really here to help, and along the way I'm also collecting Galaxy Brain badges haha 😆