# Policy question: OMP hosting unmodified antigravity-acp for one user **URL:** \ **Category:** Google Antigravity\ **Tags:** feedback, help-request-support\ **Created:** [November 12, 2026, 4:19am UTC](https://discuss.ai.google.dev/t/policy-question-omp-hosting-unmodified-antigravity-acp-for-one-user/199753 "2026-11-12T04:19:37Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Guanxiong\_Me](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/guanxiong_me/32/168329_2.png) [@Guanxiong\_Me](https://discuss.ai.google.dev/u/Guanxiong_Me)\ **Post date:** [November 12, 2026, 4:19am UTC](https://discuss.ai.google.dev/t/policy-question-omp-hosting-unmodified-antigravity-acp-for-one-user/199753/1 "2026-11-12T04:19:37Z")
Hello Antigravity team, I am an individual Google AI Pro subscriber. I use one personal Google account, on my own machine, for my own software development. I am not reselling access, rotating accounts, or sharing credentials. I have not installed this plugin and I have not signed in through it. I am asking before I do. Plugin: omp-antigravity-acp-provider 0.1.43 omp packages com The author states that it is not an official Google integration and not an official Oh My Pi integration. The source repository is SenCha930511/omp-antigravity-acp-provider. Host: Oh My Pi (OMP), a third-party terminal coding harness. It is not Zed, JetBrains, VS Code, Android Studio, Xcode, or T3 Code. How it works 1. OMP loads the plugin and registers models under the id prefix antigravity-acp/. 2. On a prompt, the plugin starts Google’s ACP server as a local child process and speaks ACP over stdio. It does not call agy -p. It does not implement Cloud Code Assist itself. 3. Runtime selection: if I set AGY\_ACP\_BIN, that executable is used. Otherwise it prefers the newer of the managed antigravity-acp binary downloaded from Google’s registry into ~/.local/opt/agy-acp/, or the ACP server bundled with the official agy CLI. For the CLI channel it generates a small wrapper and launches that bundled server through the wrapper. 4. Sign-in is Google browser consent. The plugin says it does not accept a raw OAuth token on this path, and that Antigravity keeps the credentials under ~/.gemini/antigravity-acp/. On a headless machine it intercepts the authorization URL, shows that URL to me, and relays only the 127.0.0.1 callback to Antigravity’s own listener. It says it does not persist the authorization code. 5. OMP tools can be exposed through a local HTTP MCP bridge. The plugin can also pass --dangerously-skip-permissions. 6. The model list is whatever that ACP server advertises. The README says this can include Claude and GPT-OSS, not only Gemini. 7. Intended use is single-user and interactive. I would be present. No background agents, task queues, scheduled runs, or account rotation. I am trying to match this to three earlier replies. I can link only one of them: - 25 September 2026, “Is using the official agy CLI through a local MCP server with third-party AI agents permitted?” Staff said wrapping agy -p for a third-party agent is not permitted. - 2 November 2026, “Conflicting guidance on using T3 Code with personal Google AI subscriptions.” Staff said an ACP client launching the official unmodified antigravity-acp binary with native oauth-personal is permitted for single-user interactive development, Gemini models only. - 4 November 2026, OpenBot. Staff allowed the same pattern, with limits on unattended use, third-party tools, and non-Gemini models: [ToS Clarification — Is OpenBot (official Antigravity ACP server) permitted under the Antigravity Terms of Service? - #2 by Ambati\_Rajendra](https://discuss.ai.google.dev/t/197826/2) Questions 1. If this plugin launches only the official unmodified managed antigravity-acp binary, I sign in with oauth-personal, and I use only Gemini models for single-user interactive development, is that permitted on a personal Google AI Pro account? 2. Does the answer change because the host is OMP, a third-party coding harness, rather than Zed, T3 Code, or OpenBot? 3. Does the generated wrapper around the agy CLI’s bundled ACP server make that channel non-compliant, even if the managed-runtime channel is compliant? 4. If I select Claude or GPT-OSS because the ACP server advertises it, is that outside the Gemini-only scope for general ACP clients? 5. Is intercepting the authorization URL and forwarding only the loopback callback still native oauth-personal, or an unsupported credential bridge? 6. Is exposing OMP’s own tools through a local MCP bridge the unsupported third-party tool-driver case from the OpenBot reply? 7. If this use is a violation, is enforcement limited to Antigravity and Gemini CLI access, as Section 6 states? I will not install or sign in through the plugin unless you say that configuration is permitted. If it is not, I will use only the official Antigravity app or agy CLI, or a Gemini API key from Google AI Studio. Thank you. ---
**Author:** ![Rebbanpalli\_Naveen](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/rebbanpalli_naveen/32/120945_2.png) [@Rebbanpalli\_Naveen](https://discuss.ai.google.dev/u/Rebbanpalli_Naveen)\ **Post date:** [November 12, 2026, 6:41am UTC](https://discuss.ai.google.dev/t/policy-question-omp-hosting-unmodified-antigravity-acp-for-one-user/199753/2 "2026-11-12T06:41:13Z")
Hi @Guanxiong_Me, Welcome to the Forum, Thank you for checking before installing the plugin. Based on our [Terms of Service (Section 6)](https://antigravity.google/terms), [FAQ](https://antigravity.google/docs/faq#why-cant-i-use-third-party-software-such-as-claude-code-openclaw-or-opencode-with-my-antigravity-login), and [Other editors (ACP) documentation](https://antigravity.google/docs/ide/extensions/acp), **we do not recommend installing or signing in through `omp-antigravity-acp-provider` with consumer `oauth-personal`** : - **Questions 1 & 2 (OMP Harness vs. Direct ACP Clients):** While any interactive ACP client (such as Zed, JetBrains, Xcode, T3 Code, or a custom interactive UI) may launch the unmodified `antigravity-acp` / `agy acp` binary when a human directly drives the session, wrapping `antigravity-acp` as a model provider (`antigravity-acp/*`) inside a third-party coding agent harness like Oh My Pi (OMP) is not permitted on consumer `oauth-personal` plans ([FAQ](https://antigravity.google/docs/faq#can-i-use-antigravity-cli-headless-mode-in-third-party-coding-agents-or-automate-account-switching)). - **Questions 3, 5 & 6 (Wrapper Script, OAuth Callback Relay & MCP Bridge):** Generating wrapper scripts around `agy`, intercepting/relaying the `127.0.0.1` OAuth callback instead of using native `oauth-personal` or `agy acp --login` (`terminal-login`), and driving harness tools with `--dangerously-skip-permissions` are also non-compliant on consumer sign-in ([ACP Authentication](https://antigravity.google/docs/ide/extensions/acp#authentication), [Terms Section 4](https://antigravity.google/terms)). - **Questions 4 & 7 (Models, Enforcement & Compliant Path):** General ACP clients outside supported IDEs (JetBrains, Android Studio, Zed, and Xcode) are scoped to **Gemini** models ([ACP Models](https://antigravity.google/docs/ide/extensions/acp#models-and-thinking-level)), and Section 6 enforcement applies to your **Antigravity and/or Gemini CLI** accounts ([Terms Section 6](https://antigravity.google/terms)). To use Gemini inside OMP, please use a **Google AI Studio Gemini API key** (`gemini-api-key`) instead.