They removed the ACP command line flag that was in the old Gemini client. That's a signal that they won't support it. The TOS is vague enough that one could argue that altering the usual behaviour of agy will cause it to change the shape of its traffic enough to constitute bypassing normal token usage.
While it may be technically allowed, I'm not about to risk my account. Google has proven themselves to be capricious and arbitrary when it comes to TOS enforcement, and their appeals system doesn't meaningfully exist in practice.
I am not talking about ACP command flag - there is a separate binary that exists for integration into editors, and it's how VScode extension works. So it's the same usage pattern underneath
I don't see a download link for that:
https://antigravity.google/docs/ide/extensions/
What I see is integrations for specific editors.
Agent-shell uses ACP server published through ACP registry here [1] - those are AFAIK used by editor extensions as backend since VScode can't exactly run Go-based extensions - Zed instructions explicitly talk about using ACP Registry too [2]
[1] https://github.com/agentclientprotocol/registry/blob/main/an...
It does mean however that it cannot operate as flexibly as it it could with raw API, IMO, but agent-shell is essentially designed towards wrapping the official clients