DevAgentRadar → Google Antigravity

Goal: turn this release signal into a safe pilot plan for my stack.

Context

Assistant: Google Antigravity Proposal: Install Antigravity plugins with /plugin and set Artifact Review in /config Summary: Antigravity 1.3.2 adds /plugin (and agy plugin install) for marketplace and local plugins that bundle skills, MCP servers, subagents, rules, and hooks. --dangerously-skip-permissions no longer auto-approves /plan; set Artifact Review in /config if artifacts should proceed without review. Primary source: https://github.com/google-antigravity/antigravity-cli/releases/tag/1.3.2

Why it matters

1.3.2 makes plugins a first-class way to share skills, MCP servers, subagents, rules, and hooks: browse the official marketplace with /plugin, install from the shell with agy plugin install <plugin-name>@antigravity-plugins-official, or use + Install from local directory.... Settings are collected in a form before a plugin turns on, and /plugin install|uninstall|enable|disable|list covers day-to-day management. Authors can keep the manifest in .antigravity-plugin/ or .gemini-plugin/, list skills in plugin.json, store data in PLUGIN_DATA, and ship named tools in bin/; every skills/ file loads, remote MCP servers start after settings are filled, and a plugin’s subagents can use that plugin’s MCP servers. Installs are safer (no half-installed leftovers) and the plugin list opens instantly. Separately, --dangerously-skip-permissions now only skips tool permission prompts and no longer auto-approves the implementation plan in /plan—plans wait for review unless you set Artifact Review in /config. Adopt plugins as the install path and update any scripts or habits that assumed the old skip-permissions behavior.

Suggested actions

1. In Antigravity, run /plugin, browse the official marketplace, install the plugins that bundle the skills, MCP servers, subagents, rules, and hooks this repo needs, and complete each plugin’s settings form before it turns on.
2. From a shell without opening the CLI, install a marketplace plugin with agy plugin install <plugin-name>@antigravity-plugins-official, then in the CLI run /plugin list and use /plugin enable, /plugin disable, or /plugin uninstall as needed.
3. For an internal plugin, in /plugin choose + Install from local directory... and point at a folder that has .antigravity-plugin/ or .gemini-plugin/, skills listed in plugin.json, optional skills/ and bin/ tools, and per-plugin data via PLUGIN_DATA.
4. If you previously passed --dangerously-skip-permissions so /plan would auto-approve: stop relying on that. The flag now only skips tool permission prompts; plans wait for review. Open /config and set Artifact Review only if you want plans and other artifacts to proceed automatically.
5. If you author plugins, put the manifest in .antigravity-plugin/ or .gemini-plugin/, list skills in plugin.json, ship CLI tools in bin/ for the agent to run by name, and fill remote MCP settings so those servers start and plugin subagents can use the plugin’s own MCP servers.

Config surfaces this release may change

• permission rules (high confidence) — check your repo before applying
• hooks — check your repo before applying
• MCP servers — check your repo before applying
• subagent definitions — check your repo before applying
• skills — check your repo before applying

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/google-antigravity-1-3-2-install-antigravity-plugins-with-plugin-and-set and mark Applied, Skipped, or Failed. Proposal id: ffb2db6a-f3ae-4935-9223-ea2c234b9f7a

Please:

1. Map the change to concrete pilot steps
2. Flag security / permission implications
3. Keep the pilot reversible