collaborating-with-antigravity

# Collaborating with Antigravity (agy) Use the Antigravity CLI (`agy`) as an independent collaborator while the calling agent stays responsible for verification, synthesis, and final user-facing decisions. Antigravity CLI is Google's replacement for the **retired Gemini CLI** (hosted auth shut off 2026-06-18). The bridge script (`scripts/agy_bridge.py`) wraps `agy -p` (headless print mode), returns structured JSON, and manages session continuity via `SESSION_ID`. **Always go through the bridge** — raw `agy -p` surfaces no conversation ID and no structured output (see below). ## Why the bridge is mandatory - **agy won't reveal the conversation ID** (no `--session-id`, never printed). The bridge recovers it from agy's cache, returns it as `SESSION_ID`, and resumes via `--conversation`. It also serializes calls with a file lock — **don't run bridge calls concurrently.** - **agy has no structured output.** The bridge shapes plain text into JSON, streams live progress to stderr, and enforces its own wall-clock kill as the real timeout. Mechanics, upstream issue numbers, and the verified flag surface: [references/agy-cli.md](references/agy-cli.md). Commands below write `<skill_dir>` for the absolute path of the directory containing this SKILL.md. Your harness usually reports that path when it loads the skill. If it does not, use this SKILL.md's own location. Substitute it before running, for example `~/.claude/skills/collaborating-with-antigravity`. ## Safety `agy` ca...