Antigravity CLI plugins¶

ID: antigravity-cli-plugins
Links: Home page · Documentation
Version requirement: >= 1.2.14
Platforms: 🐧 Linux · 🍎 macOS · 🪟 Windows
Operations: installed · install · remove
purl types: pkg:antigravity-cli-plugins/
CLI name: agy
Issues and PRs: 📦 manager: antigravity-cli-plugins
Source: antigravity.py

The plugins of the Antigravity CLI, agy.

A package is a plugin of the user’s profile, identified by the name its plugin.json declares, and stored under ~/.gemini/config/plugins. Plugins a project keeps in its own .agents/plugins directory are not reported: the listing covers the profile alone, whatever the working directory.

install takes a local plugin directory, or <plugin>@<marketplace> for a marketplace the Antigravity application registered: the command line has no way to add one, and no search. The plugin is then listed under its name.

The CLI itself updates with agy update, which is not a plugin operation and is left to topgrade.

What `mpm` adds to `antigravity-cli-plugins`¶

mpm reaches across every manager at once, not antigravity-cli-plugins alone: mpm installed and mpm outdated cover antigravity-cli-plugins alongside every other manager you run in one table, mpm upgrade --all updates them together, and mpm sbom exports the whole machine as one bill of materials.

Every mpm command also gains --dry-run and --plan previews, cross-scheme version comparison and purl identifiers. See manager augmentations for how each one is built.

Your `antigravity-cli-plugins` commands, in `mpm`¶

You already know antigravity-cli-plugins: each operation maps one-to-one onto mpm, in an interface shared by every manager.

To…	With `antigravity-cli-plugins`	With `mpm`
List what’s installed	`agy plugin list`	`mpm --antigravity-cli-plugins installed`
Install a package	`agy plugin install ~/plugins/apricot-notes`	`mpm install pkg:antigravity-cli-plugins/~/plugins/apricot-notes`
Remove a package	`agy plugin uninstall apricot-notes`	`mpm remove pkg:antigravity-cli-plugins/apricot-notes`

Prefix any command above with --dry-run to simulate the underlying manager calls without touching the system: the safe way to watch what mpm would do before trusting it.

Operations¶

Operation	Supported	Notes
`installed`	✅	Listings carry plugin names only, with no version.
`outdated`	❌	No command reports a newer plugin.
`orphans`
`search`	❌	No catalog is reachable from the command line: marketplaces are browsed in the Antigravity application.
`install`	✅
`upgrade`	❌	No update command: the Antigravity application updates plugins.
`upgrade_all`	❌	No update command: the Antigravity application updates plugins.
`remove`	✅
`sync`
`cleanup`
`doctor`

Configuration¶

Ignore antigravity-cli-plugins on the mpm CLI by passing the --no-antigravity-cli-plugins option.
Ignore it for every run in your configuration:
```
[mpm]
antigravity-cli-plugins = false
```

Raise the timeout of all antigravity-cli-plugins calls:

[mpm.overrides.antigravity-cli-plugins]
timeout = 900

Run mpm config-template antigravity-cli-plugins to print all overridable settings for your configuration file:

[mpm.overrides.antigravity-cli-plugins]
cli_names = [
    "agy",
]
cli_search_path = []
dry_run = false
ignore_auto_updates = true
plan = false
post_args = []
pre_args = []
pre_cmds = []
requirement = ">=1.2.14"
stop_on_error = false
unmaintained = false
version_cli_options = [
    "--version",
]
version_regexes = [
    "^(?P<version>\\d+\\.\\d+\\.\\d+)",
]

Recipes¶

A few jobs you would otherwise script around antigravity-cli-plugins, one mpm command each:

Snapshot and clone a machine: mpm --antigravity-cli-plugins dump antigravity-cli-plugins.toml, then mpm restore antigravity-cli-plugins.toml on the next one.
Export a compliance SBOM: mpm --antigravity-cli-plugins sbom (CycloneDX by default, --spdx for SPDX).

Privilege escalation¶

mpm runs this manager as the current user and never prepends sudo by default. Flip the policy for its privileged operations with --sudo or the per-manager sudo override.

None of its operations is privileged.

See privilege escalation for the full policy.

Cooldown¶

State of Antigravity CLI plugins’s release-age gating, from the cooldown support table:

Status: ❌ None

A cooldown only pays off where a compromised release can be withdrawn while the clock runs, and can only be emulated where the registry dates its releases. From the retraction table:

Registry: Antigravity plugin sources
Retraction: None: a plugin comes from a local directory, or from a marketplace the Antigravity application registers, whose format the documentation leaves undescribed
Publish date: ❌ the listing carries importedAt, the local import time, and no publication date

With --cooldown set, mpm skips this manager’s install and upgrade operations rather than run them unguarded (fail-closed); --cooldown best-effort opts back in.

Reference traces¶

A collection of raw native outputs captured from the manager’s own CLI and recorded in the manager source. If you know Antigravity CLI plugins well and a transcript below looks wrong, or a newer release changed its output format, report it.

$ agy plugin list
{
  "imports": [
    {
      "name": "apricot-notes",
      "source": "antigravity",
      "importedAt": "2026-09-30T09:08:27Z",
      "components": null
    }
  ]
}

Version check¶

The version is probed by running:

$ agy --version
1.2.14

and extracted with:

r"^(?P<version>\d+\.\d+\.\d+)"

Changelog¶

8.1.0.dev0 (unreleased)
- Add the plugin manager of the Antigravity CLI, agy, with installed, install and remove support.