Antigravity: Surfaces, Configuration Paths, and Gemini Enterprise

GCP Study Hub
November 19, 2026

Antigravity is Google's environment for agentic coding. For the Professional Agentic Architect exam, the main architectural distinctions around Antigravity involve picking the right developer surface, placing customizations in the right configuration path and folder, and using Gemini Enterprise authentication when organizational data protections and network perimeters apply.

Antigravity surfaces and editor workflows

Antigravity is available in four forms:

  • A desktop app and IDE, known as the Antigravity IDE
  • A CLI (agy)
  • An extension for JetBrains IDEs such as IntelliJ IDEA, which provides agent side panels, inline diffs, and interactive plans inside the editor developers already use
  • An SDK for building your own agents in Python

Each surface serves a distinct developer workflow. The Antigravity IDE is a full editor in its own right. The agy CLI runs in a terminal, so it works beside any editor, though its diffs and plans are not shown inside that editor. The JetBrains extension brings agent side panels, inline diffs, and interactive plans into an existing JetBrains IDE. The Python SDK is for teams that build their own agents in code.

Workspace and global configuration paths

Antigravity's behavior is customized with rules, skills, subagents, hooks, MCP servers, and plugins. Those customizations can live in a workspace's .agents folder and be committed with the code, or in a developer's global configuration under ~/.gemini/config/.

Choosing between workspace and global scope comes down to whether a customization belongs to a single repository or follows an individual developer across projects. Folders inside a workspace's .agents directory apply to that one workspace and are shared through source control when committed. Folders under ~/.gemini/config/ live on the developer's machine and are never part of a repository. For skills, that means workspace skills in .agents/skills/ and personal skills in ~/.gemini/config/skills/, which are available in every workspace the developer opens in the Antigravity IDE. Antigravity also still supports the older ~/.gemini/antigravity/skills/ location.

Folder type matters just as much as scope. Skills and rule files each have their own folder at both levels, a skills folder for skills and a rules folder for rules, and a skill is loaded as a skill only when it sits in a skills folder.

Gemini Enterprise authentication and data protections

On the Professional Agentic Architect exam, how developers sign in to Antigravity determines whether corporate governance and network controls cover agent traffic. In the JetBrains extension, developers can select Sign in with Gemini Enterprise and authenticate with their corporate identity. Enterprise support in the JetBrains extension is currently in Preview.

When developers sign in with Gemini Enterprise, Gemini Enterprise protections apply:

  • Code, prompts, and agent transcripts are never used to train Google's foundation models
  • The organization's IAM policies are respected
  • The organization's VPC Service Controls perimeter applies to agent traffic

Personal Google Accounts use each developer's individual plan instead, so these enterprise data protections and the organization's VPC Service Controls perimeter do not apply, whichever Antigravity surface the developer uses. What matters for enterprise governance is the identity a developer signs in with.

Our Professional Agentic Architect practice exams test Antigravity surfaces and configuration alongside Gemini Enterprise protections and VPC Service Controls, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow