Support keyword: antigravity cli plugins
Plugins are where many Gemini CLI extension questions land. Migrate carefully, test one plugin at a time, and review what each plugin can do.
Updated on 2026-05-27. Independent guide. Use official Google links for downloads and account actions.
Not affiliated with Google. No binaries, mirrors, login forms, or copied install commands are hosted here.
Google's transition messaging says Gemini CLI Extensions are part of the migration story, with Antigravity plugins becoming the relevant destination. That makes antigravity cli plugins a useful long-tail page: users are not just asking where a menu is, they are asking whether custom workflow pieces still exist.
Do not migrate every extension or plugin at once. Plugins can add commands, tools, context, or integrations. Each extra capability changes what the agent can see and do.
| Surface | Typical role | Migration caution |
|---|---|---|
| Plugins | Packaged capabilities, commands, or integrations. | Check what the plugin can access before enabling broadly. |
| MCP servers | External tools and data through a protocol connection. | Validate config, auth, and token storage separately. |
| Skills | Reusable instructions and workflows for the agent. | Keep workspace-specific skills close to the project. |
If a migrated workflow fails, identify which layer is missing before reinstalling everything. A plugin problem usually looks like a missing packaged capability, an MCP problem often looks like a server or OAuth failure, and a skills problem usually looks like the agent ignoring a workflow instruction. Debugging one layer at a time keeps the migration understandable.
Sources: official Google Antigravity product pages, Google Antigravity CLI documentation, and the Google Developers transition announcement. This site is an independent guide and is not affiliated with Google.
They are related in the migration story, but do not assume every extension maps perfectly. Test plugin behavior.
No. Enable one at a time and test visibility, permissions, and side effects.
MCP is a protocol connection to tools and data. Plugins are packaged capabilities inside the Antigravity ecosystem.