Antigravity CLI on your phone, on your own server

Antigravity CLI, the agy command, is Google's terminal coding agent and the replacement for Gemini CLI on personal accounts. Google already gives you a way to reach it from a phone, so start there. Then decide whether running it on your own server through Maude adds anything for you.

Google's Remote Control and what it covers

Antigravity Remote Control works with Antigravity desktop sessions and CLI instances. You start it in one of three ways:

• /remote-control inside a running session
• agy --remote-control at launch
• agy remote-control start, a headless daemon

You then open the Remote Control dashboard in a browser on any device, signed in with the same Google account. On a phone you can install it as a web app and get notifications when an agent finishes or needs input. When the agent pauses for a tool confirmation or a question, you can answer from the terminal or from the dashboard. Work continues on the host as long as it stays connected. Google's docs also say Remote Control can be turned off by an account or organisation policy flag.

That's a capable, free setup, and if Antigravity is the only agent you use, it may be all you need. Maude differs in a few concrete ways:

• A native app instead of a browser dashboard, with the same inbox and session list as your Claude Code, Codex, OpenCode and Grok Build sessions.
• Nothing to install or keep running by hand. Maude deploys its daemon over SSH and installs a pinned agy.
• Files, Git and a terminal for each session, and handoff to another agent when you want a second opinion.

Running agy on a server

Add the server in Maude by address, by pasting an ssh … command, or by scanning the QR code from curl -fsSL https://maude.pilotdev.fr/setup | sh. Any Linux or macOS machine works, x86-64 or ARM, including Alpine. The daemon then:

1. Installs agy at a version we have tested. When we pin a version, we check the build against the checksum in Google's own manifest and record its SHA-256; every install is then verified against that pinned SHA-256.
2. Turns off agy's background self-update, so the version stays the tested one until Maude moves it.
3. Runs agy in its headless stream-json mode, one long-lived process per session, and resumes the conversation if the process restarts.

Sessions keep going when the app is closed. The server dials out to Maude's end-to-end encrypted relay, so no inbound port is needed. For the manual route, installing agy yourself and keeping it alive in tmux, see our guide to running Antigravity CLI on a server.

Signing in from your phone

Google's install docs describe an SSH-friendly login: agy detects that it's on a remote machine and prints an authorisation URL instead of opening a browser. Maude drives that flow:

1. Choose Sign in with Google for Antigravity in the app.
2. Open the Google link on your phone and approve. Google shows an authorisation code.
3. Paste the code back into Maude. It's passed to agy on the server, and Maude confirms once agy can list its models.

The other option is a Gemini API key. Maude sets agy's model provider to Gemini and supplies GEMINI_API_KEY. If you later remove the key from Maude, Maude switches the provider back, but only if Maude made that change; a provider you set in agy's settings yourself is left alone. Google's pricing page lists a free individual plan alongside Google AI Pro and Ultra, which raise the limits.

How approvals work (the honest version)

This is the one place where agy in Maude behaves differently from the other agents. In headless mode, agy can't stop and ask before a tool runs. If an action needs permission, agy blocks it and reports it as denied at the end of the turn. Maude never pretends otherwise. After the turn, it shows each blocked action with three choices:

• Allow and retry adds an allow rule for that exact command or file, restarts agy on the same conversation and asks it to try again.
• Always allow adds a broader rule for that kind of action.
• Keep blocked leaves the rule list unchanged.

The rules go into agy's own allow-list in its settings file on the server, so they persist, and the app tells you so. These after-the-fact approvals show up in the inbox and as push notifications like any other.

The permission modes are: default (blocked actions offered for approval afterwards), accept edits (file edits allowed, commands still blocked and offered), plan, and yolo (agy's --dangerously-skip-permissions). agy has no read-only or auto mode to switch to. Two more limitations: text prompts only (no image attachments), and no /compact or /goal from Maude. Model and effort chips use the models your account can see.

Coming from Gemini CLI

Google announced on 19 May 2026 that from 18 June 2026, Gemini CLI and the Code Assist IDE extensions would stop serving requests for Google AI Pro and Ultra subscribers and for free users. Organisations on Gemini Code Assist Standard or Enterprise kept access. For everyone else, Antigravity CLI is the replacement, and it's why Maude supports agy and not Gemini CLI.

If you had Gemini CLI on a server, the move is mostly mechanical. Install agy, sign in again, and bring your project instructions and settings across. We cover what changed and what to use now in the Gemini CLI shutdown post.

Because agy's approvals work after the fact, some people keep it for planning and review and hand implementation to an agent that can ask first. When a session is idle you can switch it to Claude Code or Codex. The new agent gets a brief with the plan, files touched, git state and recent conversation, and switching back resumes agy's own conversation.

Frequently asked questions

What changed

• October 1, 2026 — Page published. Remote Control commands and dashboard, SSH sign-in, API-key mode and the Gemini CLI cutoff checked against Google's docs and blog on this date. Maude's agy driver verified against agy 1.2.14.