Gemini Agents runs Google’s Antigravity CLI (agy) as a partner when you ask for it: “ask Gemini” or “have Gemini build or review this”. It is never a default. Google’s FAQ, read by the author on 2026-11-13, says driving agy from another agent on a consumer plan is unsupported and can risk suspension, so the skill requires the user’s clear agreement before the first run.
A Python wrapper, agy.py, sets the boundary for each turn, checks for repository hooks and plugins, probes whether its denials hold, and judges the events a turn produced.
What You Get
- agy.py, a Python wrapper with consult, build and review modes plus —check, —probe, —dry-run and —replay
- A user-agreement step with the support status stated before any run
- A refusal to start when workspace hooks, MCP configs or plugins are present unless the owner allows it
- Recorded events and metadata so a run can be replayed and judged
- Dated notes on what the sandbox allowed and refused on the tested platform, and a list of what is not established
Common Use Cases
- Getting a requested second opinion from another model family
- Letting Gemini build a stage in its own clone with the sandbox on
- Reviewing a revision in a detached clone as an extra check beside the release reviewer
- Probing whether the CLI’s permission boundaries still hold after an update
What Makes It Unique
Most partner skills assume the CLI behaves. This one records what the CLI did when tested on one day, including a denied permission that ended a turn with exit 0 and an empty answer, and encodes those findings as checks in the wrapper. It starts with a consent gate, and no other skill in the collection names Gemini as a default. Its Not established list names untested routes, such as Linux, Windows and API-key sign-in.
Under The Hood
The skill is instructions plus a Python wrapper and its test file. When you agree to a run, the wrapper launches the agy command-line tool as a subprocess in your repository or a detached clone, passes the brief as a file, and keeps session state under the Gemini folder in your home directory. In build mode Gemini can write files and run shell commands inside its sandbox. Consult mode can still use web search, and review keeps shell writes inside the clone. The wrapper runs git commands to list files, clone and compare status, and refuses to start when it finds workspace hook or plugin entries. The check command looks at the environment and the CLI’s settings to report which sign-in route is in use, without printing credentials, and the probe command tries a network request from the sandboxed shell to confirm it is denied. The owner puts any API key in the environment; the agent never asks for one.