Disclosure: GearPicked is reader-supported. Some links on this page are affiliate links; if you buy through them we may earn a commission at no extra cost to you. This never changes what we recommend. As an Amazon Associate, GearPicked earns from qualifying purchases. Read our affiliate disclosure.
Google Antigravity Remote Agents Setup + Jules Migration Before 11 Nov
By Balwant Singh Rawat · Published · Updated · Research-based (not yet hands-on tested)
Research-based setup and migration guide. Steps, limits and eligibility are summarised from Google’s Antigravity Remote Agents docs and the Jules turndown changelog, checked 7 November 2026. We have not yet run a live Remote Agent end-to-end on a production Pro/Ultra account for this page. Follow the live docs if they differ from what you read here.
As of 8 November 2026 you have about three days of normal Google Jules use left before the 11 November 2026 read-only cutoff (wind-down 31 December 2026). In the same week Google started rolling out Remote Agents in Antigravity for personal AI Pro and Ultra subscribers (Antigravity docs; 9to5Google, 6 Nov 2026). This page is the setup + migration spine. For the export CLI itself, see How to export Google Jules data. For other cloud agents, see Best Google Jules alternatives.
What changed this week: Remote Agents in Antigravity?
Google’s docs describe Remote Agents as sessions that run in an isolated, Google-managed remote environment rather than on your laptop. Because execution is remote, agents can keep working on long-running tasks after you close the browser, sleep the machine, or switch devices.
Coverage of Antigravity App 2.29 (6 Nov 2026) also calls out Voice Mode and UI refreshes; the coding-agent headline for Jules migrants is the cloud VM model (9to5Google). Rollout is gradual — eligible accounts may not see the UI on day one.
Remote Agents vs Remote Control: which do you actually need?
Google documents two different “remote” products. Confusing them is the most common setup mistake in early explainers.
| Feature | Remote Agents | Remote Control |
|---|---|---|
| Execution environment | Isolated, Google-managed remote environment | Your own desktop workstation or server |
| Host machine requirement | Runs independently; laptop does not need to stay on | Host must remain powered on and online |
| Workspace and files | Remote Resources (GitHub, Google Drive, uploads) | Local filesystem folders, local toolchains, Git worktrees |
| Best for | Repo tasks, mobile workflows, background work while away | Local hardware, local dev servers, uncommitted local checkouts |
Source: Remote Agents docs comparison table (checked 7 Nov 2026). If you also use Remote Control, the instance switcher on antigravity.google.com switches between Remote Conversations and connected host machines.
Who can use Remote Agents?
Per Google’s Availability note (checked 7 Nov 2026):
- Yes (eligible): Google AI Pro or Google AI Ultra, signed in with a personal Google Account; gradual rollout.
- No: free plan, Google AI Plus, and business accounts (Google Workspace or Google Cloud).
Plan prices change; confirm on Google One AI plans before you subscribe. As of early November 2026, public Google One pages list AI Pro around $19.99/mo and Ultra tiers around $99.99/mo and $199.99/mo — treat those as dated list prices, not a GearPicked quote.
There is no verified consumer cash affiliate for Google AI Pro/Ultra on GearPicked. This guide is for authority and cluster traffic only.
How do I start a Remote Agent from the app, the web, and the CLI?
You can launch from the Antigravity App, any browser at antigravity.google.com, or the Antigravity CLI (docs).
Antigravity App
- In the left sidebar, click + next to Projects (or open the project selector) and choose New Remote Project.
- Optionally Add Resource (GitHub, Drive, or uploads), then Next (or Skip).
- Name the project and click Create.
- Select the project and send a prompt to start a remote conversation.
Shortcut from a GitHub repo: project selector → Remote → GitHub Repositories (Connect GitHub if needed) → pick a repo; Antigravity selects or creates a remote project for it.
Web (desktop or phone)
- Open antigravity.google.com.
- Sign in with an eligible personal Pro/Ultra account.
- Enter a prompt for a standalone remote conversation, or Create Project to attach resources first.
Antigravity CLI
- Use CLI 1.4.12 or later (
agy update). - Sign in with an eligible personal account (
/helpshows account and plan). - Start remote mode:
agy --remote-agent
Optional project targeting:
agy --remote-agent --project="My remote project"
agy --remote-agent --new-project
agy --remote-agent -c
The status line shows remote and the project name. Conversations started with --remote-agent are stored with remote projects, not as local conversations — you cannot resume a local chat by adding the flag.
How do I attach GitHub, Google Drive, and uploads?
Remote agents only see Resources attached to the remote project (docs):
- GitHub: OAuth connect; select repos. Private repos in one project must share the same GitHub user/org owner — otherwise split into separate projects.
- Google Drive: Docs, Sheets, Slides, PDFs, or folders; the agent reads them on demand.
- Uploaded files: up to 8 MiB per file, 50 files and 100 MiB per project, and 2 GiB total across your account (docs, checked 7 Nov 2026). Uploads persist in the project and stage under
/home/antigravity/upload.
In the CLI, use /projects → New project / Edit to attach the same resource types.
What does Jules export save — and what will Antigravity not import?
Google’s Jules turndown notice (29 Oct 2026) lets you export account settings, environment variables, scheduled tasks, connected repositories, memories, setup scripts, and every session (prompt, plan, activity log, patches). Code, branches and PRs already in GitHub stay in GitHub.
What the notice does not say: that Antigravity will auto-import that folder. Treat the export as a handoff archive, not a one-click migrate:
| Jules export artefact | Typical Antigravity action |
|---|---|
sources.json / repo list |
Connect GitHub and attach repos to a remote project |
scheduled-tasks.json |
Recreate as Antigravity Automations (verify schedule and permissions) |
Repo memories.md / setup scripts |
Rewrite as remote project notes / setup steps; do not paste secrets blindly |
env-variables.json |
Re-enter needed secrets in a secret store; rotate anything that was a real credential |
Session summary.md / patches |
Use as context while you continue work; open PRs still live on GitHub |
Full export steps: How to export Google Jules data.
Migration checklist before 11 Nov (and before 31 Dec)
| Date | What Google says | What to do |
|---|---|---|
| Until 11 Nov 2026 | Finish Jules sessions; normal use | Merge/close Jules PRs; run the official export; start Antigravity remote project |
| 11 Nov – 31 Dec 2026 | Jules read-only | Spot-check export vs read-only UI; finish rebuilding Automations |
| 31 Dec 2026 | Jules winds down | Do not rely on Jules UI after this date |
Checklist:
- Finish Jules sessions you still need; merge or close open PRs
- Run Google’s live export prompt →
~/jules-export(keep it out of git) - Confirm personal Google AI Pro or Ultra; check whether Remote Agents UI is visible (gradual rollout)
- Create a remote project; attach GitHub (and Drive/uploads if needed)
- Review remote permission preset (default is turbo) before sensitive repos
- Rebuild only the schedules/memories you still need; rotate secrets
- Run one small task, close the laptop, resume from phone/web to confirm the model
- Between 11 Nov and 31 Dec, spot-check a few sessions against
summary.md
Permissions, turbo default, and remote limitations
Google’s CLI docs (checked 7 Nov 2026):
- Default remote permission preset is
always-proceed (turbo)unless you change it — commands run without approval prompts. - Permission presets also include
default(ask before sensitive ops) andrequest review(ask before every command). Plan review policy can bealways askoralways proceed. - Remote sessions always use the default execution mode; plan / accept-edits / auto modes are not available remotely.
- Not available yet in remote agent CLI sessions:
--print,/codesearch,/diff,/fork,/rewind,/btw,/voice, running shell yourself with!, messaging subagents with@, and local MCP servers, plugins, and agent skills.
Change remote settings via /config (Remote Agent tab) and /permissions inside a remote session.
How do Remote Agents compare with Jules and other cloud agents?
| Antigravity Remote Agents | Antigravity Remote Control | Jules (until wind-down) | Codex Cloud / Claude Code Cloud | |
|---|---|---|---|---|
| Where it runs | Google-managed remote environment | Your host (must stay on) | Google Jules environment | Vendor-managed cloud |
| Needs laptop awake? | No | Yes | No (while sessions still run) | No |
| Plan gate | Personal AI Pro / Ultra (docs) | Separate Remote Control setup (see Remote Control docs) | Jules access until cutovers | ChatGPT / Claude paid plans (per vendor) |
| Local disk / local MCP | Not local disk; attach resources; no local MCP yet | Yes on host | Jules workspace | Per product rules |
| Jules auto-import | No — manual rebuild | N/A | Export before deadlines | Manual |
Unverified cells left blank on purpose. Pricing and quotas change — confirm on each vendor’s site. For a fuller alternatives table, see Jules alternatives.
When should I stay on Codex Cloud or Claude Code Cloud instead?
Stay (or dual-run) if:
- Remote Agents has not rolled out to your eligible account yet and you need cloud agents this week.
- You rely on a vendor feature Antigravity remote sessions still lack (for example local MCP bridging, or a GitHub Issues assignment flow closer to Copilot’s cloud agent).
- Your org uses Workspace/company Google accounts — Remote Agents are personal-account only per Google’s docs.
Brief overview and plan entry points: Best Google Jules alternatives. Related academic shutdown guide: OpenAI Prism → LaTeX alternatives.
How we’ll verify
TODO: hands-on Remote Agents. On a personal Pro or Ultra account: confirm UI visibility, create one remote project, attach a public GitHub repo, run a small task, close the laptop, resume from phone/web; compare the same task under Remote Control with the host left awake. Record agy --version, OS, and test date. Add redacted screenshots.
Sources (checked 7 Nov 2026)
- Remote Agents — Google Antigravity Docs
- Remote Control — Google Antigravity Docs
- Jules Turndown changelog (29 Oct 2026)
- 9to5Google: Antigravity Remote Agents / Voice Mode (6 Nov 2026)
- Google One AI plans
Related: How to export Google Jules data · Best Google Jules alternatives · OpenAI Prism shutting down: LaTeX alternatives · All AI tools
Frequently asked questions
Do I need Google AI Pro or Ultra for Remote Agents?
Yes for eligibility. Google’s Remote Agents docs say the feature is available to Google AI Pro and Google AI Ultra subscribers who sign in with a personal Google Account, rolling out gradually. It is not available on the free plan, on Google AI Plus, or for business accounts (Google Workspace or Google Cloud).
What is the difference between Remote Agents and Remote Control?
Remote Agents run in an isolated Google-managed environment and do not need your laptop to stay on. Remote Control drives an Antigravity session on your own workstation or server, which must remain powered on and online. Use Agents for repo/Drive/upload tasks while away; use Control when you need local files, local toolchains, or uncommitted checkouts.
Will Jules schedules, memories, and sessions import into Antigravity?
Google’s Jules turndown notice points users toward Antigravity as where Jules learnings are going, but it does not promise automatic import of sessions, memories, schedules, or settings. Treat Antigravity setup as a rebuild: export Jules first, then recreate what you still need in a remote project.
Can Remote Agents see my local uncommitted files or local MCP servers?
No. Docs say a remote agent works in its own remote environment and cannot read or change files on your machine. You attach GitHub repos, Google Drive files, or uploads. Local MCP servers, plugins, and agent skills installed on your machine are listed as unavailable in remote agent sessions.
Does the agent keep running if I close my laptop or lose Wi‑Fi?
For Remote Agents, yes — Google says execution continues even when you close the browser, sleep the laptop, or switch devices, and you can resume from the App, CLI, or web. Remote Control is different: the host machine must stay on.
What CLI version do I need for agy --remote-agent?
Google’s docs say Antigravity CLI 1.4.12 or later. Update with agy update, sign in with an eligible personal Pro/Ultra account, then run agy --remote-agent.
What is the default permission preset for Remote Agents?
Unless you change it, Google’s docs say the permission preset is always-proceed (turbo), so remote agents run commands without asking for approval. Review or change remote agent settings before starting sensitive work.
When does Jules become read-only, and when does it shut down?
Google’s Jules changelog (29 Oct 2026) says you can finish sessions until 11 November 2026. After that Jules is read-only until it winds down on 31 December 2026.