Antigravity CLI support

[grold]

Problem or motivation

Google replaces Geimini CLI with Antigravity CLI

Proposed solution

Please add Antigravity CLI support

Alternatives considered

No response

Area

Agent drivers (Claude / Codex / Gemini)

[xiaotonng]

Thanks @grold for raising this — really appreciate the heads-up on the transition.

I just spent some time installing agy (v1.0.1) and probing the integration surface. Wanted to share what I found honestly, because the picture is more complicated than a name swap:

What works in agy today

• agy -p "<prompt>" for one-shot output
• agy -c / agy --conversation <id> to resume
• --dangerously-skip-permissions, --sandbox, --add-dir
• agy plugin import gemini / import claude to inherit existing plugins

What's missing for a proper pikiclaw driver right now

• No --output-format stream-json (gemini-cli's stream protocol that pikiclaw's driver depends on). -p only emits the final assistant text — no tool-call events, no thinking events, no usage stats. All the streaming actually happens internally over a localhost gRPC "language server" whose .proto isn't public yet.
• No --model flag. Model is chosen server-side via daily-cloudcode-pa.googleapis.com:fetchAvailableModels and selected by display label in settings, not by CLI argument.
• Conversation files are encrypted protobufs (~/.gemini/antigravity-cli/conversations/*.pb). Only history.jsonl (user prompts) and cache/last_conversations.json (workspace→conversation-id map) are plaintext — we can't render session tails / messages in the dashboard the way we do for gemini-cli.
• OAuth tokens live in the system keyring (Keychain / Credential Manager / libsecret), not on disk, so the quota / usage API integration we have for gemini-cli doesn't translate.
• agy also writes a .antigravitycli/ symlink directory into every workspace it touches — pikiclaw will need to git-ignore this.

Plan

1. Short term: add agy to the External CLI catalog (Extensions → CLI) so it can be detected, installed, and surfaced — same way we treat the other CLIs.
2. Defer the full driver until Google publishes the streaming protocol (either a stream-json flag or the gRPC proto). Shipping a driver right now would give a strictly worse experience than gemini-cli — no live activity, no tool previews, no usage, no native session browsing.
3. Keep the existing gemini driver — Code Assist Standard/Enterprise users still rely on gemini-cli past the June 18 sunset, and individual users currently get a better UX there too.

Will track this issue and revisit once the protocol surface stabilises. Thanks again 🙏