Plugin marketplace arrives with /plugin, and defaults get stricter

Extending the CLI used to mean wiring up skills, MCP servers, subagents, rules, and hooks one by one. This week adds /plugin, which bundles all of them into installable packages from the official marketplace. Alongside it, several defaults get stricter: the conversation view is quieter, --dangerously-skip-permissions stops approving plans, and the macOS sandbox closes off a folder where desktop apps keep credentials.

Week 41 (October 5-10, 2026) covers versions 1.2.17 to 1.3.3: 5 releases and 51 changelog entries. Plugins are the main story, and the rest is a mix of defaults you may notice immediately and smaller fixes for /diff, scrolling, and background tasks.

---

Installing plugins from the official marketplace

What /plugin is. It is an interactive manager for the official Antigravity plugin marketplace (added in 1.3.2). You browse plugins and install them from inside the CLI. A plugin can bundle skills, MCP servers, subagents, rules, and hooks, so one install can replace several manual setup steps.

Installing from the shell. You can skip the CLI entirely and run agy plugin install <plugin-name>@antigravity-plugins-official. That suits setup scripts and fresh machines.

Installing from a local folder. In the /plugin manager, choose + Install from local directory... to install a plugin straight from a folder on your computer. This is the path to use while you develop your own plugin.

Settings before activation. If a plugin needs configuration, the CLI shows a simple form and fills in the settings before the plugin turns on. Remote MCP servers in a plugin now start correctly once those settings are filled in.

Managing what is installed. The subcommands are /plugin install, uninstall, enable, disable, and list. Disabling is handy when you want to check whether a plugin causes a problem without removing it.

Install reliability. The plugin list opens instantly. An interrupted install no longer leaves a half-installed plugin behind. Installing and removing plugins on Windows is more reliable.

Compatibility fixes. Plugins now load every skill in their skills/ folder. A plugin’s subagents can use the plugin’s own MCP servers, which matters if you bundle both and expect them to work together.

For plugin authors. Version 1.3.2 adds several options:

• The manifest can live in a .antigravity-plugin/ or .gemini-plugin/ folder.
• plugin.json can list skills.
• Each plugin gets its own data folder, available as PLUGIN_DATA.
• Command-line tools placed in a bin/ folder can be run by the agent by name.

Version 1.3.3 adds a root-level agents.json, so a plugin declares its subagents the same way it declares skills and rules with skills.json and rules.json.

---

Changes for everyday work

Verbosity defaults to medium. Since 1.3.0, the default Verbosity is medium instead of high. The conversation view groups related tool calls and thoughts into concise summaries and keeps commands and responses visible. This also applies if you picked high while it was still the default, so your view may look different after updating. To see every tool call, command, and thought in full, set Verbosity back to high in /config.

Announcement cards. Since 1.2.17, cards for model launches, deprecations, and other service notices appear above the prompt, one at a time, newest first. Press Esc on an empty prompt to dismiss the current card permanently and show the next one. Sending a message hides the card for the rest of the session.

Pinned prompt header. In no flickering mode, scrolling back through a long conversation now keeps the prompt that produced the response you are reading pinned at the top of the transcript (1.3.3). Clicking it jumps back to that prompt. In a long session this saves you from scrolling to find out what you asked.

Plans wait for review again. --dangerously-skip-permissions no longer auto-approves the agent’s implementation plan in /plan mode (1.3.2). The flag only skips tool permission prompts now. If you want plans and other artifacts to proceed automatically, set Artifact Review in /config. Check any script or alias that relied on the old behavior, because a plan that used to go through will now stop and wait.

macOS sandbox blocks Application Support. The macOS terminal sandbox now stops sandboxed commands from reading ~/Library/Application Support by default (1.3.3), since desktop apps keep credentials and session tokens there. It was readable before. You can still allow it explicitly in your sandbox rules.

---

Technical notes

Diff view. In the /diff file view, j and k now move the line cursor like the arrow keys, and left/right arrows switch files (1.3.0). Version 1.3.1 adds more: arrows open files at their first change, each file remembers its position, and n/N continue across files.

MCP. An MCP server can mark a tool as always loaded by setting antigravity/alwaysLoad to true in the tool’s _meta in the tools/list response (1.3.3).

Scrolling and paths. Trackpad and mouse-wheel scrolling no longer jumps back and forth, notably over SSH or tmux (1.3.0). Paths containing spaces, #, %, or Windows drives now work correctly in @ mentions, /codesearch results, and file links.

Tasks, agents, and rewind. Version 1.3.1 changes several things around long-running work:

• /tasks and the status line task count include timers, recurring jobs, and other background tools.
• Subagents that stop on an error show Error: with the reason in /agents instead of Done.
• Terminal notifications fire when the agent stops to ask you a question.
• /rewind in very long conversations shows cleared messages dimmed and labeled instead of failing when you select one.

Windows sandbox. The command sandbox no longer needs administrator rights, and Python, Git, and npm work inside it out of the box (1.2.17).

Images and errors. Images are scaled to at most 2576 pixels per side, which avoids failures on Claude models when a conversation has many images (1.3.2). Error messages are clearer in 1.3.3: HTML error pages show their title, long non-JSON bodies are truncated, and an expired sign-in says Authentication expired. Please log back in.

---

What to take away

If you work in the terminal.

• Open /plugin and see what the marketplace offers (whether it covers your stack is something only browsing will tell).
• Check whether the medium Verbosity suits you, and switch to high in /config if you want the full detail.
• If you use no flickering mode, scroll back through a long session and try the pinned prompt header.
• Try n/N in /diff to move across files.

If you run parallel sessions.

• Look at /tasks and the status line count, which now include timers, recurring jobs, and other background tools.
• Check /agents for the new Error: state on subagents that stopped on a failure.
• Terminal notifications now tell you when an agent is waiting on a question, so you can leave a session unattended for longer.
• /rewind in a very long conversation no longer fails on cleared messages.

If you administer integrations and company deployments.

• Review scripts that use --dangerously-skip-permissions in /plan mode. Plans now wait for review unless Artifact Review is set in /config.
• Check whether any sandboxed workflow on macOS needs ~/Library/Application Support. If it does, allow it explicitly in your sandbox rules.
• On Windows, the command sandbox works without administrator rights, which may simplify rollout.
• Try agy plugin install <plugin-name>@antigravity-plugins-official for scripted setups.
• If you maintain MCP servers, consider antigravity/alwaysLoad for tools that should always be loaded.

---

Sources: the Antigravity CLI changelog, versions 1.2.17 to 1.3.3 (October 5-10, 2026), and the Antigravity CLI documentation. Availability of features may change.