What happened
Google’s Antigravity changelog lists Antigravity App version 2.32.0, dated November 13, 2026. The release is titled “Dynamic Workflows and new themes” and contains 11 improvements and 13 fixes. One improvement targets people using Remote Agents: they can now clone Cloud GitHub repositories locally from the workspace picker and sign in to pull-request links directly in Antigravity.
The feature puts two familiar repository actions alongside the cloud-project workflow. The workspace picker is the point at which a user selects or creates a workspace; the v2.32.0 entry says a Cloud GitHub repository can be cloned locally from there. Separately, the app now supports signing in to pull-request links. Google frames both actions as Remote Agents functionality, rather than as a general repository feature for every Antigravity project.
The release follows several changes to Antigravity’s remote workflow. In the November 3 v2.29.0 release notes, Google said Remote Agents were beginning to roll out to Google AI Ultra and Pro subscribers. In a cloud project, conversations run in the cloud rather than on the user’s computer, and can also be opened at antigravity.google.com/remote. The November 9 v2.30.0 notes said Remote Agents had finished rolling out to Ultra subscribers and paid-plan Pro subscribers. That entry also added a “Configure on GitHub” link to the cloud-project repository picker for granting Antigravity access to more repositories.
Version 2.32.0 extends those repository-adjacent steps: a remote user can move from the selected Cloud GitHub repository to a local clone, then authenticate to reach related pull requests inside the app. The same release also introduces Dynamic Workflows, which let agents orchestrate parallel subagents and multi-step tasks in Python using the runtime bundled with Antigravity. It adds Everforest Light and Dark themes, prompt-navigation shortcuts, and protections for agent-controlled browser tabs. Google says Antigravity versions roll out gradually and may take a few days to reach all users.
What the archive adds
New Runtime’s November 6, 2026 earlier coverage described Antigravity Remote Agents running sessions and tools in an isolated, Google-managed remote environment. This is a new fact on that story: v2.32.0 adds local cloning of Cloud GitHub repositories and pull-request sign-in to the workflow around those cloud sessions.
Trend signal
This modestly supports agent-ready software exposes capabilities. Repository selection, local cloning, and pull-request access are bounded product surfaces around agent work rather than an undifferentiated cloud session. The release does not demonstrate a common interoperability standard or establish how permissions are represented across those surfaces, so it is a small supporting signal rather than proof of a broader shift.
Why now
The feature arrives shortly after Remote Agents became available to the relevant paid subscriber groups and after Antigravity added GitHub configuration from the cloud-project repository picker. Local cloning and pull-request sign-in address the next adjacent activities: working with a checkout and following the review trail after a cloud session has started.
Connections to other events
New Runtime’s November 6, 2026 earlier coverage focused on the remote execution boundary: sessions and tools ran in a Google-managed environment rather than the developer’s machine. This update concerns the developer-facing bridge back from that environment to a local repository and GitHub pull-request links.
Why it matters
A cloud agent is only useful to an engineering team if its work can enter ordinary repository practices without creating a separate, opaque lane. Developers still need to inspect a checkout, understand the branch and repository context, and follow review links. The new workspace-picker action and in-app sign-in make those transitions part of the Antigravity interface.
For a team evaluating the product, this is more consequential than a theme or navigation update because it connects execution location to the places where code is usually examined and changed. It is not evidence that Antigravity has automated code review, merge approval, or repository governance. Teams should instead read it as a workflow-integration increment: cloud sessions can be paired more conveniently with a local clone and pull-request access, while existing review and authorization practices remain the operational control points.
Limits and uncertainty
Google’s v2.32.0 release notes describe the local-clone and sign-in actions, but do not provide measured adoption, completion-time, or reliability results. They do not specify the authorization sequence a user sees, which GitHub repository arrangements can use the action, or how a local clone relates to changes created during a cloud session. Google also says releases reach users gradually over several days. The practical effect therefore depends on account eligibility, rollout state, and each team’s existing GitHub setup.
Skill to build now
Map the handoffs in one cloud-agent task before treating it as an autonomous delivery path. Start a Remote Agents project with a non-critical repository, identify where the workspace is selected, clone it locally through the picker, and follow a pull-request link after signing in. Use that run to document who may authorize repository access, who checks the local diff, and what review remains mandatory before any merge.
Reader takeaway
Antigravity v2.32.0 gives Remote Agents users a more direct bridge from a cloud project to a local GitHub checkout and pull-request links. The meaningful change is not greater agent autonomy; it is less friction at the boundary where remote agent work returns to normal developer review and repository practice.