Antigravity Remote Agents run agent sessions in an isolated, Google-managed environment rather than on your machine. Tasks keep going if you close the browser, sleep the laptop, or switch devices. App changelog v2.29.0 (3 November 2026) says remote agents are starting to roll out alongside voice mode. Official X posts on 6 November describe independent cloud VMs and attaching GitHub plus Drive in one project.
Not Remote Control
Docs draw a clear line: Remote Agents use Google-managed cloud environments and Remote Resources (GitHub repos, Drive files, uploads). Remote Control still drives your own workstation, which must stay online. Do not confuse the two when you migrate habits from local sessions.
Who gets it, and how
Availability is personal Google AI Pro or Ultra only, rolling out gradually. It is not on free, Plus, Workspace, or Google Cloud business accounts. You can start from the Antigravity App (New Remote Project), from antigravity.google.com, or from the CLI with agy --remote-agent on CLI 1.4.12+. Attach GitHub, Drive, or uploaded files (upload caps: 8 MiB per file, 50 files / 100 MiB per project, 2 GiB account total). Default remote permission preset is always-proceed (turbo) unless you change it. Local MCP servers, plugins, and skills on your machine are not available inside remote sessions.
Why this matters
If you already live in Antigravity after the Jules wind-down and the Code Assist sales sunset, Remote Agents are the always-on cloud lane for repo work without leaving a laptop awake. Check plan eligibility and the turbo default before you point it at anything sensitive, and keep Remote Control for work that truly needs local hardware or uncommitted checkouts.
The Campfire
CommentsThanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.
Add a comment