Builtin

Skill 14 of 23

Antigravity Support

Use when the user asks questions, seeks help, or requests instructions related to installing, setting up, or migrating to Antigravity CLI.

2 minutes · 387 words · 8 sections

Install

$ npx skills add google-gemini/gemini-cli --skill antigravity-support

$ npx skills add google-gemini/gemini-cli

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Antigravity CLI Support

This skill provides up-to-date information on how to install, configure, use, and migrate to Antigravity CLI, sourced from the official documentation at https://antigravity.google/docs/cli-getting-started (opens in a new tab).

What is Antigravity CLI?

Antigravity CLI is a next-generation terminal interface for collaborating with autonomous agents on local codebases. It is designed to be highly interactive and agent-driven, launching a Terminal User Interface (TUI) to coordinate code generation, reasoning, and workspace tasks.

Key Features:

Autonomous Agent Collaboration: Work directly with agents within your terminal.
Interactive TUI: A full terminal user interface designed for agent workflows.
Workspace Integration: Deep understanding of your local workspace structure and context.

Installation

To install the Antigravity CLI on your machine:

macOS / Linux (Fast-Path Script)

Run the following standard curl command in your terminal:

curl -fsSL https://antigravity.google/cli/install.sh | bash

This script downloads, verifies, and installs the latest version of Antigravity, and automatically registers the agy binary in your PATH.

Windows (PowerShell)

For Windows environments, install via the official PowerShell setup command:

irm https://antigravity.google/cli/install.ps1 | iex

Initial Setup & Configuration

Once installed, navigate to any project or workspace directory and run:

agy

This command starts the Antigravity CLI. The first time you launch it, the interactive TUI will guide you through:

Workspace Trust Verification: Confirming trust for the workspace folder to allow secure local command execution and file edits.
Visual Theme Configuration: Setting up your preferred interactive terminal aesthetic and layout.
Rendering Modes: Tailoring TUI performance and drawing behaviors to your terminal capabilities.

How to Migrate to Antigravity CLI

If you are transitioning or migrating from another tool (such as Gemini CLI) to Antigravity CLI, follow these steps:

Check Requirements: Ensure your local environment meets standard requirements (e.g., node, git, shell access) and is running a compatible operating system (macOS, Linux, or Windows).
Install Antigravity: Run the installation script above to make the agy command globally available.
Verify Installation: Test the installation by running agy --version or launching agy in an empty or sample directory.
Transition Workspaces: Run agy directly inside your project workspace root. The initial setup assistant will guide you to import or configure trust policies, similar to those you might have used previously.

Official Resources and Learning More

If you need more details or have advanced configuration/migration needs, please visit the official documentation:

Official Documentation: https://antigravity.google/docs/cli-getting-started (opens in a new tab)

About this skill

Trigger

Use when the user asks questions, seeks help, or requests instructions related to installing, setting up, or migrating to Antigravity CLI. This skill provides the latest up to date details, requirements, and commands sourced from the official Antigravity CLI documentation.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/google-gemini/gemini-cli, branch main, last pushed 24 September 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

23 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 4 distinct layouts observed: .gemini/skills/*/SKILL.md, packages/core/src/skills/builtin/*/SKILL.md, tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/*/SKILL.md, tools/gemini-cli-bot/.gemini/skills/*/SKILL.md.

Authorship

4 of 23 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 288°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “8 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

2 editorial notes across 2 of 23 skills. They are printed in the margin of each skill rather than as errors here.

Code Explorer — 1 note
Spec Generator — 1 note

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /google-gemini/gemini-cli.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Antigravity CLI Support

Key Features:

Autonomous Agent Collaboration: Work directly with agents within your terminal.

Interactive TUI: A full terminal user interface designed for agent workflows.

Workspace Integration: Deep understanding of your local workspace structure and context.

To install the Antigravity CLI on your machine:

Run the following standard curl command in your terminal:

curl -fsSL https://antigravity.google/cli/install.sh | bash

This script downloads, verifies, and installs the latest version of Antigravity, and automatically registers the agy binary in your PATH.

For Windows environments, install via the official PowerShell setup command:

irm https://antigravity.google/cli/install.ps1 | iex

Once installed, navigate to any project or workspace directory and run:

agy

This command starts the Antigravity CLI. The first time you launch it, the interactive TUI will guide you through:

Workspace Trust Verification: Confirming trust for the workspace folder to allow secure local command execution and file edits.

Visual Theme Configuration: Setting up your preferred interactive terminal aesthetic and layout.

Rendering Modes: Tailoring TUI performance and drawing behaviors to your terminal capabilities.

If you are transitioning or migrating from another tool (such as Gemini CLI) to Antigravity CLI, follow these steps:

Check Requirements: Ensure your local environment meets standard requirements (e.g., node, git, shell access) and is running a compatible operating system (macOS, Linux, or Windows).

Install Antigravity: Run the installation script above to make the agy command globally available.

Verify Installation: Test the installation by running agy --version or launching agy in an empty or sample directory.

Transition Workspaces: Run agy directly inside your project workspace root. The initial setup assistant will guide you to import or configure trust policies, similar to those you might have used previously.

If you need more details or have advanced configuration/migration needs, please visit the official documentation: