antigravity-delegate

Antigravity Delegate

Use Antigravity CLI through the agy command as a low-friction, large-context helper for bounded research, exploration, summarization, advisory review, and support. Codex remains responsible for deciding whether to delegate, judging the answer, editing files, implementing changes, and making final calls.

When to Use

• A task spans 3+ files or a single large file that would otherwise require chunking.
• The user asks exploratory questions like "what does this module do", "summarize this log", or "describe this flow".
• You need a research summary from long local context before Codex plans or implements.
• You want a quick second opinion on design, risk, or refactor direction before Codex decides what to do.
• You want an advisory review of a large diff to surface likely risks, missing tests, or unclear areas before Codex performs the final review.
• You need a compact summary of long logs, stack traces, generated output, PR diffs, or trace files.

When NOT to Use

• The task is a final code review, merge gate, or final architecture decision.
• The task is writing code, applying edits directly, or acting as the main coder.
• The work touches security-sensitive logic: auth, authorization, crypto, secrets, payments, BLE/PKE, or protocol correctness.
• The task is small enough for Codex to handle directly, such as a single function or a change under roughly 50 lines.
• The output would be shipped externally without Codex checking and rewriting it first.
• The task depends on live system state Antigravity cannot see, such as Redis keys, MQTT topics, deployed config, or private runtime data.

Delegation Workflow

1. Run every Antigravity CLI invocation outside the sandbox. Antigravity uses local credentials/session state that are not available inside the sandbox, so sandboxed calls can block or fail before doing useful work.
2. Confirm agy exists before relying on it:

which agy || { echo "Antigravity CLI not found"; exit 1; }