Google's Antigravity coding environment now lets you hand work to agents that run in the cloud rather than on your own machine. The version 2.29 update, dated November 3, 2026 in the changelog, introduced Remote Agents alongside a redesigned conversation page and a Voice Mode powered by Gemini Live. For developers and knowledge workers, the big change is that a task can keep going when your laptop is closed. Here is how to get started and what to check first.
Before You Begin
Remote Agents are rolling out to Google AI Pro and Ultra subscribers on personal Google Accounts. Google's wording about eligibility has varied, so confirm your plan on the official pages before you set up a workflow that depends on it. Workspace and Google Cloud business accounts may not have access yet.
Decide which work is appropriate to hand off. Remote sessions run in an isolated, Google-managed environment, and they work with GitHub repositories, Google Drive files and uploads rather than your local folders. Tasks that involve a single repository or a clear set of documents are the best starting point.
Step 1: Create a Remote Project
Start by creating a remote project in the cloud. Attach the resources the agent needs. You can add a GitHub repository, which is cloned and mounted automatically after you authorize it through OAuth. You can also add Google Drive files that the agent reads on demand, or upload files directly.
Upload limits are worth noting. The documented caps are 8 MiB per file, 50 files and 100 MiB per project, and 2 GiB per account. Large datasets will need to be trimmed or linked through Drive.
Step 2: Connect Your Tools
Connect any plugins the task requires. The reporting lists GitHub, Drive, Docs, Sheets, Slides and Calendar, each linked through OAuth. Google says credentials are encrypted at rest. Connect only the services a given task actually needs, because every connection widens what the agent can reach.
Step 3: Start a Session
You can start a session from the desktop app, from the web at antigravity.google.com, or from the command-line tool using its remote-agent option, which requires version 1.4.12 or later. Once a session is running, it keeps working even if you close the browser or put the laptop to sleep.
To check progress, use the remote sessions page on your phone. Google says you can unblock permissions from your phone, which lets you approve a step without returning to your desk.
Step 4: Watch the Permission Setting
Permission defaults deserve attention. One walkthrough notes that the command-line tool's remote preset runs commands without asking for approval. That is efficient for long jobs, but it means the agent can execute commands while you are away. Use a narrower approval setting for anything touching production systems, and review the work before merging.
Treat the output as a draft. Ask the agent to summarize what it changed, run the project's tests, and open a pull request you can review, rather than pushing directly to a main branch.
Using Voice Mode
Voice Mode sits next to the existing microphone and is powered by Gemini Live. It lets you speak requests to the agent, choose from several voices, and set playback speed between 0.75 times and 2 times. Voice is most useful for quick direction changes while you are reviewing other work, not for detailed specifications, which are easier to write down.
What Else Changed in 2.29
The update also redesigned the conversation page so the prompt box sits at the bottom of the screen, added a new default font and theme, and refreshed the Automations page. If you use Antigravity daily, expect the interface to look different after updating.
Data handling is the other thing to think through. With Remote Agents, the work and the files it touches live in a Google-managed environment rather than on your own machine, so check your organization's data policies before attaching sensitive repositories or documents.
Tips for Better Results
- Give each remote task a clear goal, a list of files it may touch and a definition of done.
- Keep tasks small enough to review in one sitting, even if the agent runs them overnight.
- Use separate projects for separate repositories so permissions and context stay clean.
- Check which account and plan you are using, since access and limits can differ across tiers.
Why It Matters
Remote agents change the rhythm of development. Work can continue while you sleep or travel, and you can review results when it suits you. That is a real productivity gain, but it also moves more risk into the background. The more autonomy you grant, the more important it is to set narrow permissions, define success clearly and review output carefully.
