Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / antigravity

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-antigravity-the-official-plugin-marketplace-reached-the-cli-in-1-3-2-one-command-installs-skills-mcp

The official plugin marketplace reached the CLI in 1.3.2: one command installs skills, MCP servers, subagents, rules, hooks and agent-runnable binaries. 1.3.2 adds /plugin as “an interactive manager for the official Antigravity plugin marketplace” and agy plugin install <plugin-name>@antigravity-plugins-official from the shell. Plugins bundle “skills, MCP servers, subagents, rules, and hooks”, can “ship command-line tools in a bin/ folder that the agent can run by name”, get a per-plugin PLUGIN_DATA folder, and show a settings form before turning on. 1.3.3 lets any MCP server mark a tool always loaded with _meta: {"antigravity/alwaysLoad": true} so the agent gets it directly, and lets plugins declare subagents in a root agents.json. 1.3.4 fixes agy plugin list showing only imported plugins; it now lists marketplace installs with version and enabled state and takes --json. 1.3.1 stops marketplace installs overwriting a plugin folder that came from a different source, and 1.2.11 starts plugins dropped into ~/.gemini/config/plugins disabled when their MCP server needs configuration. The marketplace docs add that plugins installed in Antigravity 2.0 “are automatically updated” and appear in the CLI, and that agy plugin install https://github.com/<owner>/<repo> installs from any GitHub repository.

Channel: tagged-release; cross-surface plugin sync and GitHub-URL installs are docs-only. Half: both. Date: 2026-10-08 (1.3.2), with 1.2.11, 1.3.1, 1.3.3 and 1.3.4.

Operator consequence: Installing a plugin is installing code: its hooks run on lifecycle events, its MCP servers start, and its bin/ tools become commands the agent can call by name; under always-proceed, the mode --dangerously-skip-permissions uses, every plugin MCP tool has run without a prompt since 1.1.21. Inventory with agy plugin list --json on 1.3.4, because earlier builds hid marketplace installs from that list. Plugins installed through the desktop app update themselves and change what the CLI loads without any CLI action, so disable the ones you need to audit. Review MCP servers you did not write for the alwaysLoad flag. The capability half is real: a versioned, one-command install replaces hand-copied skills and MCP config.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-antigravity-the-official-plugin-marketplace-reached-the-cli-in-1-3-2-one-command-installs-skills-mcp

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. Antigravity CLI
    tagged commit file2026-10-13-antigravity-the-official-plugin-marketplace-reached-the-cli-in-1-3-2-one-command-installs-skills-mcpgoogle-antigravity/antigravity-cli / CHANGELOG.md#L9tagged commit file2026-10-13-antigravity-the-official-plugin-marketplace-reached-the-cli-in-1-3-2-one-command-installs-skills-mcpgoogle-antigravity/antigravity-cli / CHANGELOG.md#L10tagged commit file2026-10-13-antigravity-the-official-plugin-marketplace-reached-the-cli-in-1-3-2-one-command-installs-skills-mcpgoogle-antigravity/antigravity-cli / CHANGELOG.md#L11tagged commit file2026-10-13-antigravity-the-official-plugin-marketplace-reached-the-cli-in-1-3-2-one-command-installs-skills-mcpgoogle-antigravity/antigravity-cli / CHANGELOG.md#L9official docs2026-10-13-antigravity-the-official-plugin-marketplace-reached-the-cli-in-1-3-2-one-command-installs-skills-mcpweb.archive.org/web/20261010222428/https://antigravity.google/docs/marketplace

Versioned source: run artifact