Antigravity CLI
Status: target
Novice Summary
Use this page when you mean Antigravity from the command line. It is a target, not supported, because the current product requires provider-owned metadata proof before CLI support is final.
Surface
Standalone AGY / Antigravity CLI conversations.
Plain English version: this is command-line Antigravity, not the Antigravity agent window.
Delivery Method
Historical implementation used AGY conversation discovery and resume/print mode. Current policy requires provider-owned MCP metadata, so the final method must include a programmatic metadata patch or equivalent provider-supported metadata path.
Installer Action
Target behavior: install CLI MCP config and apply a robust metadata patch when the CLI is discovered and selected.
The installer should not precheck this feature merely because Antigravity agents are present. Agent support and CLI support are separate.
Requirements
| Requirement | Needed |
|---|---|
| Patch | Required for final metadata compliance unless provider supplies metadata natively. |
| Extension | No VSIX. |
| MCP | Required. |
| Config | CLI MCP config. |
Test Status
Historical response-backed proof exists, but current support requires new proof with provider-owned metadata.
Known Risks
- Quota/auth can block testing.
- CLI session storage may change.
- Environment-only sender identity is not accepted as final support.
Architecture Rationale
The CLI remains target because the product requirement changed from “can we make it reply” to “can we make it reply with provider-owned identity in a robust way.” That is the right tradeoff for supportability.