openclaw - 💡(How to fix) Fix [Feature]: Add ACP support for Antigravity CLI (agy)

Feature request

Please consider adding first-class ACP support for the Antigravity CLI (agy) in OpenClaw.

Why this would be useful

Antigravity CLI is already useful as an interactive coding and generation agent. In local testing, agy can:

• Run non-interactively with agy -p
• Resume conversations with agy --conversation=<id> or agy -c
• Switch models through /model
• Use its own tools, including image generation
• Access models such as Gemini 3.5 Flash, Gemini 3.1 Pro, Claude Sonnet/Opus 4.6 Thinking, and GPT-OSS 120B

However, OpenClaw currently cannot treat agy as a proper ACP-capable agent in the same way it can work with other CLI agents. This makes it harder to use Antigravity as a durable OpenClaw backend for session orchestration, subagent work, inspection, and media/tool workflows.

Desired behavior

Add an Antigravity CLI ACP integration or bridge so OpenClaw can:

• Start an agy session through the normal OpenClaw session/subagent system
• Send prompts and receive structured responses over ACP
• Preserve and resume agy conversation IDs
• Expose session status/history in OpenClaw tools
• Support model selection or model override where possible
• Forward attachments/reference images where possible
• Surface generated artifacts, especially image outputs, back to OpenClaw
• Handle long-running agy tasks without blocking the main OpenClaw session
• Normalize errors such as auth failure, model unavailability, and tool permission prompts

Example use cases

• Use agy as a selectable subagent runtime from OpenClaw
• Run Antigravity CLI tasks from Discord/Telegram/WhatsApp through OpenClaw
• Generate images through agy, then automatically return the output attachment to the chat
• Compare Antigravity model behavior against Codex/Claude agents from the same OpenClaw session
• Let OpenClaw inspect, resume, or terminate stuck agy tasks cleanly

Current workaround

The current workaround is to call agy -p or run interactive agy manually from a shell, then parse terminal output and locate generated files. This works for experiments, but it is brittle:

• Output paths and artifacts need manual parsing
• Interactive flows can hang
• Session state is not visible to OpenClaw
• No standard ACP-style status/history/tool event stream is available
• Model switching is manual

Suggested implementation direction

An ACP bridge around agy could wrap:

• agy -p <prompt> for one-shot execution
• agy --conversation=<id> / agy -c for resumable sessions
• agy -i for interactive mode if needed
• Conversation metadata from ~/.gemini/antigravity-cli/
• Generated artifacts under ~/.gemini/antigravity-cli/scratch/

Even a minimal first version that supports one-shot execution, resumable conversation IDs, status reporting, and artifact discovery would make Antigravity much more useful inside OpenClaw.

Thanks for considering this.