Remote Control

Antigravity Remote Control allows you to securely connect to and drive your Antigravity 2.0 desktop sessions running across your machines from any web browser.

As AI agents take on larger-scope tasks—such as full-subsystem refactorings, extensive test suite runs, and complex dependency migrations—operations can run for extended periods. Remote Control untethers you from your physical desk while preserving your entire local development environment.

Enabling Remote Control in Antigravity 2.0

You can enable Remote Control directly from the Antigravity 2.0 Settings:

Open the Settings panel by pressing Cmd + , (or Ctrl + , on Linux/Windows), or click Settings at the bottom of the left sidebar.
Navigate to the App section.
Toggle Enable Remote Control to On.
(Optional) Set a custom Nickname (e.g., workstation-primary or server-machine) to easily identify this machine in your instance list.

Connecting from a web browser

To access your remote Antigravity instance:

Open your web browser on any device and navigate to the Antigravity Remote Control Dashboard. (Tip: On mobile devices, you can optionally install the web app to your home screen to receive push notifications when agents complete tasks or request input.)
Sign in with the same Google Account that you used on your desktop application.
In the instance switcher, select the machine you want to control.
You now have full access to view active conversations, start new agent tasks, review implementation plans, and inspect artifacts.

Install Remote Control headless daemon

The headless daemon is built into the Antigravity CLI.

Install the CLI and sign in once: run agy, complete the sign-in flow, then exit.
Register and start the daemon:

agy remote-control start

The daemon is installed as an OS service (a systemd user service on Linux, a LaunchAgent on macOS, or a Scheduled Task on Windows) and starts immediately.

Run agy remote-control status to see this machine’s instance name, then open the Antigravity Remote Control Dashboard to find it.

Managing 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

Windows notes

Registering the daemon to start at boot requires an Administrator prompt. PowerShell and Command Prompt both work.
From a normal prompt, start still works, but if your machine gets logged out/restarted, the daemon will only resume after you log back in: it cannot start on boot.
status and stop work from a normal prompt.

The credentials you used to sign into the CLI are used by the daemon for auth. This sign-in is separate from the Antigravity editor’s on the same machine.

Naming your machine (headless daemon)

For headless daemon instances, the instance name is how the machine appears in Remote Control:

Set it with the --name flag:
```
agy remote-control start --name "my-workstation"
```
Re-running start --name with a new value renames the machine.
If you never set a name, the daemon generates a friendly one (like my-machine-distant-plume) on its first start. agy remote-control status shows the current name.
To rename by editing the settings file instead, open the file below, change the value of cliRemoteControlHostname, save, and run agy remote-control start again to restart the daemon. The new name appears in the Hub once the service restarts — edits do nothing while it’s running.

Settings file locations

OS	Settings file
Linux / macOS	`~/.gemini/config/config.json`
Windows	`%USERPROFILE%\.gemini\config\config.json`

When the daemon runs

	Linux	macOS	Windows
Starts	at boot, nobody needs to log in	when you log in	at boot (Administrator install); at login otherwise
Keeps running after you sign out	yes	no — back at next login	yes, with a boot install
Comes back by itself after a crash	yes	yes	yes — up to 3 restart attempts, then at the next boot or by running `agy remote-control start` again

Troubleshooting

Antigravity 2.0 Desktop

Machine Does Not Appear in the Web UI:
- Ensure that Enable Remote Control is toggled on in Antigravity 2.0 Settings on your host machine.
- Verify that your host machine has an active internet connection and is not asleep or suspended.
- Check that you are signed in with the same Google Account in both the desktop app and the web browser.
Reconnection and Disconnects:
- If your local network connectivity drops temporarily, the web interface automatically tries to reconnect. Any running background agent tasks and shell commands will continue executing on your host machine uninterrupted as long as the host maintains an internet connection.

Headless Daemon

Machine doesn’t show up in the Hub — run agy remote-control status. If it reports sign-in problems, run agy, sign in, then run agy remote-control start again.
Checking the logs:
- Linux: journalctl --user -u antigravity-cli-daemon -n 50
- macOS: ~/Library/Logs/antigravity-cli-daemon.log
- Windows: the newest cli-*.log under %USERPROFILE%\.gemini\antigravity-cli\log
Rename didn’t take effect — the name is read when the daemon starts; run agy remote-control start again.
Windows: daemon only starts at login, not at boot — start was run from a non-Administrator prompt. Re-run agy remote-control start from an elevated prompt for start-at-boot.
Connection keeps dropping and reconnecting — an old script-installed daemon may still be registered and fighting this one for the connection. Run agy remote-control start again; it removes the old service automatically.
Two similar entries in the Hub — one is the editor, one is this daemon. They’re separate on purpose; rename whichever one you mean.

Next Steps

Settings Overview: Explore all configuration options in Antigravity 2.0.
Permissions & Security: Configure security presets and tool access rules.