[FEATURE] Google Antigravity CLI (agy) Support

[intoffset]

Greetings,

Google Antigravity CLI (agy) is becoming another agent harness that teams may want to support alongside Claude Code, Codex, Gemini CLI, Cursor, Windsurf, and other APM targets.

APM already supports Gemini CLI, but Antigravity CLI appears to use its own configuration surface and should probably be treated as a separate target rather than folded into the existing gemini target.

Is your feature request related to a problem? Please describe.

Yes. Teams that use APM as the source of truth for agent context currently cannot declare Antigravity CLI as an install/compile target.

A project can still rely on AGENTS.md as shared context, but Antigravity-specific primitives such as workspace skills, rules, plugins, and MCP configuration are not represented in APM's target list or deployment logic.

Describe the solution you'd like

Add Google Antigravity CLI (agy) as a supported APM target.

Likely target mapping to validate against current Antigravity CLI docs:

• Target name: antigravity or agy
• Shared project instructions: AGENTS.md
• Workspace skills: .agent/skills/
• Workspace rules: .agent/rules/
• MCP configuration: Antigravity mcp_config.json / plugin-based configuration
• Plugin support: Antigravity CLI plugins can contain skills, agents, rules, MCP servers, and hooks

This would let APM deploy the same managed skills/instructions to Antigravity CLI without users manually symlinking or copying .agents/skills into .agent/skills.

Describe alternatives you've considered

• Treating Antigravity CLI as Gemini CLI: this seems risky because agy has a distinct plugin/config layout and runtime behavior.
• Relying only on AGENTS.md: useful as a baseline, but it does not cover Antigravity workspace skills/rules/MCP configuration.
• Project-local symlink from .agent/skills to .agents/skills: workable as a stopgap, but not a first-class APM target.

Additional context

Antigravity CLI docs indicate support for plugins, MCP, skills, and workspace context/rules. The CLI also has a plugin subcommand for installing/importing/managing plugins.

Related existing APM work:

• feat(gemini): add Gemini CLI as supported target with integration tests #917 added Gemini CLI as a supported target.
• [FEATURE] Kiro Support #702 tracks Kiro support and is a similar multi-target support request.

Happy to provide local examples or help test a target implementation against agy.

Gemini CLI sunset: https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/
MCP: https://antigravity.google/docs/mcp
Skills: https://antigravity.google/docs/skills
Rules: https://antigravity.google/docs/rules-workflows
Plugins: https://antigravity.google/docs/plugins
Hooks: https://antigravity.google/docs/hooks
"Sidecars" (completely new vs others apparently): https://antigravity.google/docs/sidecars

[danielmeppiel]

Gemini CLI sunset: https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/
MCP: https://antigravity.google/docs/mcp
Skills: https://antigravity.google/docs/skills
Rules: https://antigravity.google/docs/rules-workflows
Plugins: https://antigravity.google/docs/plugins
Hooks: https://antigravity.google/docs/hooks
"Sidecars" (completely new vs others apparently): https://antigravity.google/docs/sidecars

[github-actions]

Triage Panel Verdict -- Issue #1650

[FEATURE] Google Antigravity CLI (agy) Support

Thank you @intoffset for the thorough and well-referenced feature request.

---

Panel Summary

Dimension	Decision
Type	type/feature
Area	area/multi-target
Theme	theme/portability
Priority	priority/high
Status	status/accepted (pre-existing, human-applied -- preserved) + status/triaged
Milestone	Defer to maintainer

---

Persona Findings

DevX UX Expert

Well-scoped feature request. The author has done the upfront mapping work (target name, skills path, rules path, MCP config surface, plugin model). Direct analogues exist in #917 (Gemini CLI) and #702 (Kiro), which makes the implementation path clear. The Gemini CLI sunset link confirms this is not speculative -- Antigravity CLI is the canonical successor. Low UX regression risk; this is an additive target extension.

Supply Chain Security Expert

File write paths (.agent/skills/, .agent/rules/, mcp_config.json) follow the same pattern as existing APM targets. No novel exposure at the triage layer. The "Sidecars" primitive is genuinely new relative to other targets and warrants a careful implementation review during the PR phase -- it is unclear whether sidecars can execute code or only declare metadata. Flag this surface in the implementing PR for a security pass before merge. No blocker here.

OSS Growth Hacker

Gemini CLI is being sunset in favor of Antigravity CLI (confirmed by the author's blog post link). APM already supports Gemini CLI; failing to support its successor would be a regression for existing Gemini CLI users migrating to agy. Being among the first package managers to ship Antigravity support is a growth opportunity. Priority should be elevated accordingly.

Python Architect

New integrator class following the BaseIntegrator pattern. Config surface is well-defined by the author. The Sidecar concept may require a new abstraction or an extension to the existing primitive model -- this is the only genuinely novel design question. Recommend the implementing PR include a brief design note on sidecar handling before landing. Overall: moderate complexity, clearly bounded scope.

APM CEO Arbiter

Acceptance is already decided (pre-existing status/accepted). The Gemini CLI sunset makes this time-sensitive for existing users. Classify priority/high. No dimension conflicts between personas. Ship when bandwidth allows; do not let it slip past the next minor release cycle.

---

Suggested Next Action

Open an implementation PR for the antigravity (or agy) target integrator, following the same structure as the Gemini CLI integrator (#917). Include a brief design note in the PR body on how Sidecars will be modeled -- either as a new primitive type or as an extension of existing plugin/skill handling.

---

Triage status: agentic proposal pending human ratification.
Silence is approval. Maintainers can:

• Override any label or milestone above by editing it directly --
  human edits are authoritative and will not be reverted on
  subsequent runs.
• Re-trigger triage by applying the status/needs-triage label, or
  by removing status/triaged to enroll the issue in the next
  daily sweep.

Posted by the Triage Panel workflow. See .apm/skills/apm-triage-panel for the panel skill.

Generated by Triage Panel · sonnet46 921.6K · ◷