Google Antigravity Remote Control: How to Control the Agent from Your Phone

If you haven’t installed Antigravity yet, start with an overview of what Google Antigravity is and how to install it. This guide is for when an agent is already handling a long task (refactoring, running tests, migrating dependencies) and you need to step away from your desk while keeping control of the session.

What is Remote Control in Google Antigravity?#

Remote Control is a Google Antigravity feature that lets you securely connect to desktop and CLI sessions on your machines and control them from any web browser. According to the official description, large tasks—for example, a full subsystem refactor, a long test run, or a complex dependency migration—can take a long time. Remote Control lets you manage a session while away from your computer, keeping your entire development environment local.

The feature works both in the desktop app 2.0 and in the CLI—the terminal version of Antigravity (agy)—but it is enabled and behaves differently in each.

Enabling Remote Control in Desktop Antigravity 2.0#

You can enable Remote Control in the app settings:

1. Open the Settings panel with Cmd + , (or Ctrl + , on Linux and Windows), or click the Settings button at the bottom of the left panel.
2. Go to the App section.
3. Switch Enable Remote Control to On.
4. (Optional) Set a Nickname, such as workstation-primary or server-machine, so you can easily recognize this machine in the list of connected devices.

Connecting from a Phone or Another Browser

To open a remote session:

1. Open a browser on any device and go to the Antigravity Remote Control Dashboard. On a phone, you can also install the web app on your home screen to receive push notifications when the agent finishes a task or asks for your response.
2. Sign in with the same Google account you use on the desktop.
3. Select the desired machine in the device switcher.
4. Once connected, you can see active conversations; you can start new tasks for the agent and view implementation plans and artifacts.

If the machine doesn’t appear in the web interface, the official instructions say to check three things: the Enable Remote Control toggle is on on the computer running Antigravity; that computer has an internet connection and hasn’t gone to sleep; and the desktop app and browser use the same Google account.

If the network connection temporarily drops on the device you’re using to connect, the web interface will try to reconnect automatically. The agent’s background tasks and commands launched from the terminal continue running on the computer with Antigravity without interruption, as long as it remains connected to the internet.

Two Remote Control Modes in Antigravity CLI#

The CLI has two modes: an interactive mode tied to a specific terminal process, and a background headless daemon that runs without an open terminal.

Interactive Mode: /remote-control

You can enable Remote Control in the current interactive agy session without restarting the CLI. Run this in the input line:

/remote-control

According to the official description, the CLI opens a connection—a reverse tunnel—for the current session and prints the hostname along with a link to the active conversation for another device:

Remote control on for this session.
Hostname: devbox-swift-falcon
Open https://antigravity.google.com/r/<instance-id>?p=c%2F<conversation-id> on another device to continue this conversation.

Open this link in a browser on a laptop, tablet, or phone, sign in with the same Google account you use in the CLI, and continue working in the session through the Antigravity web interface.

To disable the tunnel without ending the local terminal session:

/remote-control off

You can start the CLI with Remote Control already enabled by using a flag at startup:

agy --remote-control

Interactive mode is tied to the agy process: when you exit the CLI (/exit, Ctrl+C, Ctrl+D) or close the terminal window, the Remote Control tunnel ends automatically, and the session entry disappears from the dashboard. Each interactive CLI process has its own session ID and hostname, so you can run agy --remote-control simultaneously in several terminal tabs or working directories.

When you connect to an interactive CLI session from a browser, both sides sync in real time. Requests from the remote device go straight to the local terminal, while the agent’s reasoning, tool calls, and code changes are visible in the remote interface. If the agent pauses to ask for confirmation (y/n) or asks a follow-up question, you can respond from your phone or the local terminal. Settings are the exception: you can’t change them from the remote web interface, only from the CLI itself.

Headless Daemon: agy remote-control start

The second mode is a persistent background daemon that registers as an OS service. It is available while the machine is on and connected to the internet; behavior after logout and reboot depends on the platform.

agy remote-control start

The daemon registers as an OS service (a systemd user service on Linux, a LaunchAgent on macOS, or a Scheduled Task on Windows) and starts immediately, without an open terminal window.

Use agy remote-control status to see the entry name. Then select this machine on the Antigravity Remote Control Dashboard and continue working through the Antigravity web interface.

Three commands control the daemon:

agy remote-control start     Register and start the daemon
agy remote-control status    Show the daemon's status and instance name
agy remote-control stop      Stop the daemon and unregister it

The daemon uses the credentials you used to sign in to the CLI. Signing in to the CLI is separate from signing in to the Antigravity desktop editor on the same machine; in the browser, use the same Google account as in the CLI.

You can set the headless daemon’s machine name with the --name flag at startup:

agy remote-control start --name "my-workstation"

Running start --name again with a new value renames the machine.

If you don’t set a name, the daemon generates a memorable one (such as my-machine-distant-plume) on its first launch; agy remote-control status shows the current name. You can also rename it in the settings file: open ~/.gemini/config/config.json on Linux/macOS or %USERPROFILE%\.gemini\config\config.json on Windows, change the value of cliRemoteControlHostname, save the file, and run agy remote-control start again to restart the daemon. The new name will appear on the dashboard after the service restarts; changes to the file do not take effect while the daemon is running.

There are two similar fields in the file. cliRemoteControlHostname is the CLI daemon name used here. remoteControlHostname is a separate field for the Antigravity desktop editor on the same machine; in Antigravity 2.0, you can change it in Settings → App.

How the Daemon Behaves After Logout and Reboot

Behavior depends on the OS:

Windows-Specific Details

Registering the daemon for autostart at system boot requires running as an administrator. You can use either PowerShell or the regular command prompt. The start command will also work from a regular window, but after logout or reboot, the daemon will resume only at the next login, not at boot. The status and stop commands work from a regular window without elevated privileges.

Which Mode to Choose

The interactive mode is enough to manage a current task from your phone. If you need remote access without an open terminal, use the headless daemon, subject to your OS conditions.

What to Do If You Have Connection Problems#

Problems and solutions from the official documentation:

For deeper diagnostics, check the daemon logs: on Linux, run journalctl --user -u antigravity-cli-daemon -n 50; on macOS, check ~/Library/Logs/antigravity-cli-daemon.log; on Windows, check the newest cli-*.log in %USERPROFILE%\.gemini\antigravity-cli\log.

The headless daemon provides access without an open terminal, including when you’re away, subject to the computer and OS operating conditions. If you no longer need persistent access, stop the daemon with agy remote-control stop.

There is a separate article about remote control in Claude Code. To control another agent through Telegram, see setting up Hermes Agent in Telegram.

What’s Next#

If you work in the CLI and want to step away from the current task, start with interactive mode. Leave the terminal open: if you close it, the tunnel disconnects and the session entry disappears from the dashboard. To access the machine without an open terminal, use the daemon subject to your OS limitations.

More materials are available on Ailoot.