Google's Antigravity Launches Remote Agents That Keep Coding While You Sleep

Google is gradually rolling out Remote Agents for Antigravity, its agentic coding environment. The feature runs complete coding sessions in isolated, Google-managed cloud workspaces, allowing tasks to continue after the browser closes or the local machine sleeps. Access currently requires a personal Google Account with a Google AI Pro or Google AI Ultra subscription.

Remote execution gives Antigravity an asynchronous workflow for refactors, dependency upgrades, test runs, and other jobs that may take longer than an interactive session. Developers can start work in the Antigravity web app , leave it running, and resume the same conversation later from the web, desktop app, or command-line interface.

Cloud sandboxes replace local sessions

Each remote conversation receives its own sandboxed workspace. The agent runs its tools there and cannot access the local filesystem, so source code and supporting material enter the workspace through project Resources.

• GitHub repositories: Repositories connected through OAuth are cloned and mounted automatically.
• Google Drive files: Docs, Sheets, Slides, PDFs, and folders are read on demand during a conversation.
• Uploaded files: Individual files may be up to 8 MiB, with a 100 MiB limit per project and a 2 GiB limit per account. Uploads are staged under /home/antigravity/upload .

All private repositories attached to one project must belong to the same GitHub user or organization owner. Work spanning private repositories from multiple owners requires a separate remote project for each owner, preserving credential boundaries at the cost of additional project setup.

Start or resume from the CLI

Remote Agent support requires Antigravity CLI version 1.4.12 or later. The relevant commands are:

The CLI status line displays remote and the active project name. When a user exits, the CLI prints the command needed to resume that specific conversation.

Autonomy arrives switched on

Remote Agents use the always-proceed (turbo) permission preset by default, allowing commands to run without approval. The default preset pauses before sensitive operations, while request review requires approval before every command. Repository and Drive access should be scoped with this unattended execution model in mind.

Plan Review Policy separately controls whether the agent pauses for approval of implementation plans. Remote sessions always use the default execution mode, which is distinct from the permission preset; the plan , accept-edits , and auto execution modes are unavailable.

Remote mode has sharp edges

Several Antigravity CLI capabilities remain unavailable during remote sessions:

• Non-interactive print mode through --print .
• Code search through /codesearch .
• History commands including /diff , /fork , /rewind , and /btw .
• Voice dictation through /voice .
• Direct shell commands entered with ! .
• Subagent messaging entered with @ .
• Locally installed MCP servers, plugins, and agent skills.

Remote plugins must be connected through Antigravity’s Marketplace. Available integrations include GitHub, Google Drive, Google Docs, Google Sheets, Google Slides, and Google Calendar. Google says OAuth credentials are encrypted at rest and tokens are injected when a request needs them.

Rollout excludes work accounts

Remote Agents are rolling out to Google AI Pro and Google AI Ultra subscribers signed in with personal Google Accounts. The feature is unavailable on the free and Google AI Plus plans, as well as through Google Workspace and Google Cloud accounts. That account restriction prevents organizations from adopting the managed service through their business identities during the initial rollout.

Remote Agents versus Remote Control

Antigravity already supports remote work through Remote Control, which lets a browser operate CLI sessions running on a Linux virtual machine, virtual private server, container, or other user-provisioned host. Remote Agents remove that infrastructure setup by placing the workspace and agent runtime in Google’s environment.

Jobs can outlive the laptop

Remote Agents fit tasks that benefit from unattended execution, including large refactors, long test suites, dependency upgrades, CI investigations, and exploratory repository work. Conversation state follows the user between supported Antigravity clients, while the cloud workspace keeps running independently of the originating device.

The managed environment reduces setup while introducing clear constraints around account eligibility, private repository ownership, local extensions, and command approval. Developers evaluating the feature can find configuration and rollout details in the Remote Agents docs .