Antigravity CLI 1.5: ACP, Remote Agent and Projects

Q: How do I use Antigravity CLI with Zed or JetBrains via ACP?

Install Antigravity CLI, confirm agy acp --help works, sign in with an interactive agy session or agy acp --login, then register command agy with argument acp as a custom agent in your editor. The editor launches agy acp as a subprocess over JSON-RPC on stdin/stdout. VS Code needs a community ACP Client extension.

Q: How do I start a remote agent session in the CLI?

Run agy --remote-agent. Optionally pass --project="Name or ID" to target an existing remote project, or --new-project to create one named after the current directory. Conversations keep working if your laptop sleeps; attach GitHub repos or files to the remote project so the agent has code to edit.

Last updated: November 5, 2026

Antigravity CLI 1.5 (agy) ships ACP so editors can run Google’s agent in their own chat panel, plus –remote-agent for Google-managed remote sessions, local multi-folder /projects, partner plugin MCP sign-in, and Nov 4–5 reliability fixes. Upgrade with agy update, then try agy acp –help or agy –remote-agent.

Contents

What changed in 1.5.0 and 1.5.1
Use agy acp in your editor
Remote Agents from the CLI
Local /projects workflows
Plans, credits and limits
Compared with 1.4 and Gemini CLI
FAQ
Sources

What changed in 1.5.0 and 1.5.1

Google published Antigravity CLI 1.5.0 on 2026-11-04 (UTC) and 1.5.1 on 2026-11-05 (UTC). These sit on the October 1.3–1.4 line covered in our Antigravity CLI October 2026 guide.

Headline 1.5.0 features from the GitHub release notes:

agy acp — Agent Client Protocol server over stdio for editors, with images and file context, turn steering, default / accept-edits / plan modes, session/resume, per-session model and thinking level, and agy acp --login for SSH or headless editors.
agy --remote-agent — run conversations on Remote Agents; --project selects a remote project by ID or name; header shows remote workspace; terminal-unfriendly artifacts get an Open in browser link.
Local /projects — list, create (name + folders), rename, change folders, and switch projects in a local session.
Partner plugin MCP sign-in during /plugin install, plus ${HOME} in plugin sidecar.json templates.
Headless -p without --print-timeout waits for background tasks; a print timeout exits with code 3 and an AGY_ERROR line. /btw side questions can call tools (permission-gated calls are auto-denied).

1.5.1 broadened ACP model choice to every model on your account for every ACP client, renamed remote-session /config tabs to TUI and Remote Agent, cut post-command wait when a background process still holds stdout (about 1 second instead of 5), labeled blocked subagents with the waiting tool, tightened plugin OAuth token exposure in the sandbox, and fixed ACP cancel/resume races plus Windows CRLF, UTF-8, and MCP process leaks.

Use agy acp in your editor

Official docs describe ACP as the way to run Antigravity CLI inside Zed, JetBrains IDEs, Android Studio, Xcode, and other ACP clients. The editor starts agy acp as a subprocess and speaks JSON-RPC over stdin and stdout. VS Code is not native ACP; Google points to a community ACP Client extension.

Install or update: curl -fsSL https://antigravity.google/cli/install.sh | bash on macOS/Linux, or the PowerShell installer on Windows; then agy update if you already have it.
Confirm ACP: agy acp --help.
Sign in with interactive agy, or run agy acp --login (useful over SSH).
Register the agent. In Zed settings.json, add an agent_servers entry of type custom with command agy and args ["acp"].
Start a new Antigravity thread in the editor agent panel. Use absolute which agy if the editor does not inherit your shell PATH.

1.5.0 documents session modes default, accept-edits, and plan, plus session/resume without replaying history. 1.5.1 fixed hanging prompts on close/reload/resume. See Other editors (ACP) and the CLI ACP page.

Remote Agents from the CLI

Remote Agents run tools in an isolated, Google-managed environment so long jobs continue when your laptop sleeps. Docs contrast them with Remote Control, which still needs your own machine online.

Feature	Remote Agents	Remote Control
Execution	Google-managed remote environment	Your desktop or server
Host online?	Not required after start	Host must stay powered and online
Files	Remote resources (GitHub, Drive, uploads)	Local folders, toolchains, worktrees
Best for	Repo tasks, mobile, background work	Local servers, uncommitted checkouts
CLI entry	`agy --remote-agent` (1.5.0+ in –help; docs say 1.4.12+)	Separate Remote Control flow

Availability: Google AI Pro or Ultra with a personal Google Account; not free, not Google AI Plus, not Workspace/Cloud business accounts; gradual rollout. Start with agy --remote-agent, optionally --project="My remote project" or --new-project. Attach repositories through /projects because the remote environment cannot see your local disk. Details: Remote Agents docs. Also see Google AI Pro vs Ultra.

Local /projects workflows

Projects group one or more folders, isolated agent settings, and conversation history. Docs contrast the old single-folder workspace with projects that can span frontend and backend checkouts and add project-scoped permissions. In CLI 1.5.0, local sessions gain full /projects management: list (current marked), create from name + folders (absolute, ~, or workspace-relative), rename, change folders, and switch (adds folders and starts a new conversation). See Projects overview.

Plans, credits and limits

Official Plans copy: Ultra gets the highest quota refreshed every five hours; Pro gets a high quota refreshed every five hours until a weekly limit; other users get a meaningful weekly quota. The CLI statusline can show remaining credits, /credits opens usage and upgrade links, and "useG1Credits": true in settings.json (or Use AI Credits in /config) controls spend. Follow in-CLI portal links plus Plans and CLI AI credits.

Compared with 1.4 and Gemini CLI

1.4.x focused on Auto mode, /compact, faster /diff, image paste, and sandbox hardening—without first-class ACP or CLI Remote Agent flags in agy --help. 1.5 is the editor-integration and remote-execution release. Google is transitioning users from Gemini CLI toward Antigravity CLI; see Gemini CLI 0.67 and Is Gemini CLI free?. Closest third-party CLIs remain Claude Code and Codex CLI 0.166.

Plan around these limits: Remote Agents need an eligible personal Pro/Ultra account and attached remote resources; ACP clients vary (VS Code needs a community extension); headless print timeouts now exit 3; plugin OAuth tokens are only injected into Authorization headers inside the sandbox after 1.5.1.

FAQ

What is new in Antigravity CLI 1.5?

Versions 1.5.0 (2026-11-04) and 1.5.1 (2026-11-05) add agy acp as an Agent Client Protocol server for editors, agy –remote-agent for Google-managed remote sessions, local multi-folder /projects management, partner plugin MCP sign-in, and reliability fixes for Windows, ACP sessions, and plugin OAuth in the sandbox.

How do I use Antigravity CLI with Zed or JetBrains via ACP?

Install Antigravity CLI, confirm agy acp –help works, sign in with an interactive agy session or agy acp –login, then register command agy with argument acp as a custom agent in your editor. The editor launches agy acp as a subprocess over JSON-RPC on stdin/stdout. VS Code needs a community ACP Client extension.

Who can use Antigravity Remote Agents?

Official docs state Remote Agents are available to Google AI Pro and Google AI Ultra subscribers signed in with a personal Google Account, rolling out gradually. They are not available on the free plan, Google AI Plus, or business accounts (Google Workspace or Google Cloud). Docs recommend CLI 1.4.12 or later; 1.5.0 surfaces –remote-agent in agy –help.

How do I start a remote agent session in the CLI?

Run agy –remote-agent. Optionally pass –project="Name or ID" to target an existing remote project, or –new-project to create one named after the current directory. Conversations keep working if your laptop sleeps; attach GitHub repos or files to the remote project so the agent has code to edit.

What does /projects do in Antigravity CLI 1.5?

In a local session, /projects lists your projects (current marked), creates a project from a name plus folders (absolute, ~, or workspace-relative paths), renames a project or changes its folders, and switches projects so those folders join the workspace and a new conversation starts.

How do Antigravity CLI AI credits work?

The CLI statusline can show remaining AI credits. /credits opens a credits panel with usage detail and links to buy credits or upgrade. settings.json supports "useG1Credits": true, and /config can toggle Use AI Credits. Baseline quotas differ by Google AI Pro, Ultra, and free plans per the Plans page.

Antigravity CLI 1.5: Power-User Guide to ACP, Remote Agents and Projects