On the Paseo daemon host, download your platform's archive from the official ACP Registry. Extract the entire archive, keeping the companion localharness_external executable beside the server. The ordinary agy CLI does not replace this server.
| Platform | \nExecutable | \nPlugin-supplied arguments | \n
|---|---|---|
| macOS ARM64 | \nagy_acp_server.par | \nNone | \n
| Linux x64 / ARM64 | \nagy_acp_server.par | \n--uid= | \n
| Windows x64 / ARM64 | \nagy_acp_server.exe | \nNone | \n
Add the extraction directory to the daemon's PATH, or set PASEO_AGY_ACP_BIN to the executable's absolute path. For example:
export PASEO_AGY_ACP_BIN=\"$HOME/.local/share/antigravity-acp/agy_acp_server.par\"\nSet this in the environment that starts the daemon; exporting it in another terminal does not change a running daemon. Restart the daemon after changing its environment. The login terminal also needs Node.js 22.18+ and the same server configuration.
\npaseo plugin add 3ae3ae/paseo-plugin-agy-provider\nFor an existing installation, run paseo plugin update agy-provider. The login menu requires plugin v0.1.1+ and Paseo 0.8 on the client.
Cmd+K on macOS) and choose Antigravity: Log in with Google.agy-provider. For a remote daemon, authentication runs on that host; the helper does not relay OAuth callbacks to another machine.See VERIFICATION.md for tested behavior and versions.
","readmeText":"# agy-provider\n\nUse Google's official **Antigravity ACP server** in [Paseo 0.8](https://paseo.sh/docs/plugins/v0.8/providers). This is a community-maintained plugin.\n\n> [!IMPORTANT]\n> **Paseo's injected system prompts and the instructions they contain are not applied.**\n> Official ACP server 1.1.1 ignores these instructions. Workflows that rely on them are unsupported by this plugin. Review this limitation before installing.\n\n**Known issue in Paseo 0.8.0:** streamed replies can appear as separate blocks with large gaps, splitting words, lists, and Markdown formatting. Reported upstream: [paseo#4699](https://github.com/getpaseo/paseo/issues/4699). This plugin currently has no workaround.\n\n\n\nCaptured model picker and conversation. [Desktop](images/conversation.jpg) · [Compact layout](images/compact.jpg)\n\n## Installation\n\n### 1. Install the official server\n\nOn the **Paseo daemon host**, download your platform's archive from the [official ACP Registry](https://github.com/agentclientprotocol/registry/blob/main/antigravity-acp/agent.json). Extract the entire archive, keeping the companion `localharness_external` executable beside the server. The ordinary `agy` CLI does not replace this server.\n\n| Platform | Executable | Plugin-supplied arguments |\n| --- | --- | --- |\n| macOS ARM64 | `agy_acp_server.par` | None |\n| Linux x64 / ARM64 | `agy_acp_server.par` | `--uid=` |\n| Windows x64 / ARM64 | `agy_acp_server.exe` | None |\n\nAdd the extraction directory to the daemon's PATH, or set `PASEO_AGY_ACP_BIN` to the executable's absolute path. For example:\n\n```sh\nexport PASEO_AGY_ACP_BIN=\"$HOME/.local/share/antigravity-acp/agy_acp_server.par\"\n```\n\nSet this in the environment that starts the daemon; exporting it in another terminal does not change a running daemon. Restart the daemon after changing its environment. The login terminal also needs **Node.js 22.18+** and the same server configuration.\n\n### 2. Install the plugin\n\n```sh\npaseo plugin add 3ae3ae/paseo-plugin-agy-provider\n```\n\nFor an existing installation, run `paseo plugin update agy-provider`. The login menu requires plugin v0.1.1+ and Paseo 0.8 on the client.\n\n### 3. Log in\n\n1. Open a workspace in Paseo.\n2. Open the **Command Center** (`Cmd+K` on macOS) and choose **Antigravity: Log in with Google**.\n3. Complete Google's browser sign-in. The **Antigravity login** workspace terminal shows progress and the result; use its sign-in link if the browser does not open.\n4. If the model list still shows an earlier authentication error, reload `agy-provider` in Settings → Plugins.\n\n**No separate clone or npm install is needed.** The action uses the helper already included in the installed plugin.\n\nThe official server owns authentication and credential storage. Existing ACP authentication can be reused; ordinary `agy` CLI login alone is insufficient. If you override `GEMINI_HOME`, use the same value for the daemon and login terminal.\n\n### Gemini API key instead of Google sign-in\n\nSet `GEMINI_API_KEY` securely in the daemon's launch environment. Merge this into `~/.gemini/antigravity-acp/settings.json`, preserving other settings:\n\n```json\n{\n \"auth\": { \"type\": \"gemini-api-key\" }\n}\n```\n\nUse the corresponding path under `GEMINI_HOME` if overridden, and restart the daemon to load the environment. Both the key and `auth.type` are required. This route needs no browser or login-helper invocation. See [Google's authentication options](https://antigravity.google/docs/ide/extensions/zed).\n\n## Usage\n\nChoose **Antigravity** in the model picker, or run:\n\n```sh\npaseo run --provider agy \"Explain this project's entry point.\"\n```\n\nModels and modes come from the official server and your account.\n\n```sh\npaseo plugin update agy-provider\npaseo plugin reload agy-provider\npaseo plugin remove agy-provider\n```\n\nUpdate the official server separately. Removing the plugin leaves Google's server, credentials, and conversations intact. Release-pinned installations do not track updates; remove and re-add with a newer `--ref` to change the pin.\n\n## Limitations\n\n- Real-agent verification covers macOS ARM64 and personal Google OAuth. Linux/Windows sessions, API-key and enterprise authentication, and physical mobile devices are unverified.\n- In-place steering and structured output guarantees are not implemented.\n- The current server/shim can display duplicate tool rows.\n- The login action requires an open workspace and the default plugin ID `agy-provider`. For a remote daemon, authentication runs on that host; the helper does not relay OAuth callbacks to another machine.\n\nSee [VERIFICATION.md](VERIFICATION.md) for tested behavior and versions.\n\n## Troubleshooting\n\n| Symptom | Check |\n| --- | --- |\n| Executable not found | Daemon PATH or `PASEO_AGY_ACP_BIN`. |\n| `Internal error` opening a session | Keep the companion executable beside the server; extract the full archive. |\n| `Authentication required` | Use the login action, or check API-key configuration. |\n| Login menu missing | Update the plugin, use a Paseo 0.8 client, and open a workspace. |\n| No models after login | Reload the plugin; check `paseo provider diagnostic agy`. |\n\nPlugin startup logs: `paseo plugin logs agy-provider`. Remove credentials, OAuth links, and private content before sharing logs.\n\n## Development\n\n```sh\nnpm ci\nnpm run typecheck\nnpm test\npaseo plugin install /absolute/path/to/paseo-plugin-agy-provider\n```\n\nThe provider uses `runAcpProvider()`; the login action reuses Paseo's terminal. There are no plugin runtime dependencies or build steps.\n\n[Contributing](CONTRIBUTING.md) · [Code of Conduct](CODE_OF_CONDUCT.md) · [Security reports](SECURITY.md)\n\n## License\n\n[MIT](LICENSE) covers this repository's code. Google's proprietary server is installed separately under [Google's terms](https://antigravity.google/terms).\n"}