Antigravity Remote Control: Control Agents from Anywhere

You just assigned a large, complex coding task to your AI Agent: refactoring an entire payment architecture, writing hundreds of integration tests, or running a large database migration. This task might take 45 minutes to several hours. You want to grab lunch, take a coffee break, or head home, but the Agent is running locally on your workstation where all your private git repositories, local databases, Docker daemons, and environment secrets live.

If you step away, the agent might pause on a critical terminal tool approval (human-in-the-loop) and sit idle for hours.

This is why Antigravity Remote Control was introduced in Google Antigravity 2.0 — allowing developers to securely connect, monitor, and steer their AI agents from any web browser on any device.

1. Explain Like I’m 10 (ELI5)#

Imagine your AI coding assistant is a smart robot mechanic working inside your private garage (your workstation):

• The garage has all your specialized tools, private parts, and confidential blueprints.
• Normally, you have to stand right beside the robot all day to press a green “Approve” button whenever it wants to use a heavy power tool.
• Antigravity Remote Control is like a secure pocket walkie-talkie with a touchscreen: You can walk across town, look at your phone to see what the robot is building, read its blueprints (Artifacts), and tap “Approve” instantly whenever it asks.

All the heavy tools and private blueprints stay securely inside your garage — your phone acts purely as a secure remote steering window.

flowchart LR
    subgraph Remote["Mobile Device / Secondary Laptop"]
        Browser["Web Browser<br/>(Mobile / Tablet / Laptop)"]
    end

    subgraph Cloud["Security & Relay Layer"]
        Gateway["Google Account Auth<br/>& Secure Relay"]
    end

    subgraph Host["Primary Workstation / Server"]
        Daemon["Antigravity 2.0 Engine<br/>(Desktop App / Headless Daemon)"]
        Workspace["Local Workspace<br/>(Git, Docker, Secrets, Shell)"]
    end

    Browser <-->|HTTPS / WebSocket<br/>End-to-End Auth| Gateway
    Gateway <-->|Encrypted Tunnel| Daemon
    Daemon <-->|Direct Execution| Workspace

2. The Problem: Local Power vs. Mobility#

Prior to native Remote Control, software engineers faced recurring workflow bottlenecks:

1. Desk Tethering: Agentic workflows on large codebases take substantial execution time. Developers were forced to stay at their desks simply to keep an eye on things.
2. Approval Bottlenecks: For security reasons, sensitive shell commands and plan revisions require human confirmation. Stepping away meant paused agents and lost momentum.
3. Fragile and Insecure Ad-hoc Workarounds: Relying on SSH port-forwarding, VNC/TeamViewer, or third-party reverse proxies often introduced high latency, heavy bandwidth consumption, clunky mobile interactions, and serious credential exposure risks.

3. Core Features of Antigravity Remote Control#

Google Antigravity 2.0 provides a polished, cloud-relayed remote management experience:

• Multi-Instance Hub: Switch between multiple workstations effortlessly from a single browser tab (e.g., your personal MacBook for frontend, an on-prem GPU rig for ML tasks, and a remote cloud devbox).
• Live Session Streaming: Inspect real-time conversation transcripts, review implementation plans (implementation_plan.md), and preview generated artifacts and file diffs.
• Human-in-the-Loop Approvals: One-tap approval or rejection for shell commands, subagent delegations, and file writes directly on your phone.
• Proactive Push Notifications: Receive mobile alerts the moment an agent finishes a milestone or requires your input.
• Headless Daemon Support: Run lightweight agent engines on headless Linux or macOS servers without needing a graphical desktop environment.

4. Step-by-Step Setup Guide#

Step 1: Enable Remote Control in the Desktop App#

1. Launch Antigravity 2.0.
2. Press Cmd + , (macOS) or Ctrl + , (Windows/Linux) to open Settings.
3. Navigate to the Account tab.
4. Toggle Enable Remote Control to On.
5. (Optional) Set a friendly Nickname (e.g., MacBook-Pro-M3 or Studio-Workstation) to easily recognize your machine in the web dashboard.

[!NOTE] For Remote Control to function, your host machine must stay powered on, connected to the internet, and prevented from entering deep sleep mode.

Step 2: Set Up Headless Daemon (For Cloud VMs & Linux Servers)#

If you are running agent workflows on headless cloud servers or CI environments, install the official Antigravity Daemon:

curl -fsSL https://antigravity.google/cli/agy-daemon.sh | bash

Once installed, launch the daemon in the background:

agy-daemon start --name "gpu-server-prod"

Step 3: Connect from Any Web Browser#

1. Open your browser on your phone, tablet, or secondary laptop.
2. Visit the Remote Control portal: https://antigravity.google/docs/remote-control/ (or the Antigravity Web Dashboard).
3. Sign in with the same Google Account authenticated on your host machine.
4. Select your active instance from the device switcher.

+-------------------------------------------------------------+
|  Antigravity Remote Control Hub                             |
+-------------------------------------------------------------+
|  [● Online]  MacBook-Pro-M3 (Workspace: blog)       [ Open ] |
|  [● Online]  gpu-server-prod (Workspace: ml-pipeline) [ Open ] |
|  [○ Offline] office-desktop                                 |
+-------------------------------------------------------------+

Step 4: Steer and Approve Agent Actions Remotely#

Once connected, you can prompt the agent, monitor subagent progress, review architectural decisions, and approve terminal commands on the fly.

# Agent proposes running full test suite on host machine
$ bun run test:coverage
[Prompt Approval Required: Accept (Y) / Deny (N)] -> Tap Accept on mobile

5. Security Best Practices#

[!WARNING] Because Remote Control provides live access to execute shell commands and modify local files, always secure your Google Account with strong 2-Factor Authentication (2FA) or hardware Passkeys.

• Session Isolation: Remote sessions are tied directly to your verified Google Identity and encrypted in transit.
• Headless Keyring Readiness: On headless Linux systems, ensure your system keyring daemon (e.g., GNOME Keyring or Secret Service) is unlocked to allow secure agent credential retrieval.
• Strict Sandbox Defaults: Maintain sandbox boundaries so agents only execute commands within authorized project directories unless explicitly elevated.

6. Summary#

Antigravity Remote Control eliminates the physical boundary between developers and their local development environments. You maintain the full privacy and local power of your primary machine while enjoying the freedom to monitor and steer autonomous AI workflows from anywhere.

References#

• Google Antigravity Remote Control Documentation ↗
• Google Antigravity Official Docs Overview ↗
• Antigravity CLI and Headless Daemon Guide ↗