Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Antigravity's remote agents run in Google's cloud

Written November 13, 2026

Antigravity's remote agents do the work Jules used to take — in Google's cloud, on Ultra and paid Pro plans. What Google says they are.

What a remote agent is

Google's Remote Agents documentation describes sessions and tools that run in an isolated, Google-managed remote environment rather than on your local machine. Because the work happens remotely, a session keeps running on long tasks and keeps executing commands after you close the browser, put the laptop to sleep, or move between a desktop and a phone. Nothing on your own machine needs to stay powered on or online.

That is a different shape from Antigravity's Remote Control, which drives sessions on your own workstation or server and needs that host to stay on. Remote Agents trade the local filesystem for attached resources: the workspace is built from what you connect to a remote project, not from folders on your disk.

Who can use them

Access sits behind a personal Google Account on an eligible plan. Google's documentation names Google AI Pro and Google AI Ultra subscribers, signed in with a personal account. The free plan, Google AI Plus, and business accounts on Google Workspace or Google Cloud do not get remote agents. A team whose developers sign in with company Workspace accounts cannot hand them this surface today, however the rest of their Antigravity setup looks.

You can start and manage a remote agent three ways: from the Antigravity App on the desktop, from the Antigravity CLI in a terminal, or from any desktop or mobile browser at antigravity.google.com. In the app, a remote project sits alongside local projects; on the web, you sign in and either send a prompt for a standalone remote conversation or create a project first.

What a remote project holds

The Jules succession, briefly

Google is winding Jules down, and its notice points users toward Antigravity. The practical question for a Jules user is whether remote agents cover the old job: hand over a repository task, leave, and come back to the result. On Google's own description, that is the shape remote agents take — repository work and background execution while you are away — with the plan gate and the personal-account rule as the two conditions to meet first. The export and shutdown details live on the Jules pages linked below.

Limits

Related playbooks

Sources

Back to: Coding tasks playbooks hub · Also: Google Jules ends Nov 11: export your work · Export Jules work and rebuild scheduled tasks before the shutdown · Antigravity CLI 1.5.7: Auto becomes the default