shitanshuuppal/agy-call

## What it does
Claude Code can hand work to Google's Gemini through the agy CLI (Antigravity): a coding task, a review, a question, or a batch of tasks.
This repository is the Claude Code plugin agy and the command-line runner agy-call behind it.
Calling agy directly caused two problems.
When a reply came back in the wrong format, it was thrown away and the question was asked again in a new conversation, so the paid-for answer was lost.
When one task ran out of Gemini quota, the other tasks running at the same time did not find out and kept sending requests that could not succeed.
agy-call sits between Claude and Gemini and handles both:
It saves every reply to disk before checking it, so no paid reply is lost.
When a reply is unusable, it goes back to the same conversation and tells Gemini what to fix, instead of starting over.
When one call hits the quota limit, it records a hold for the whole machine; every other call checks the hold before launching and waits until the limit resets.
It can check answers for you, for example requiring valid JSON with certain fields, and sends a reply back when the format is wrong.
A call can run in the background; agy-call status, result and cancel show how it is going, print its answer and stop it.
It can hand a coding task to Gemini in its own git worktree and branch, with a permission grant made for that task only, and merge the checked result locally.
It can have Gemini review the current change in a read-only snapshot and return a checked list of findings, each with a severity, tied to the exact code reviewed.
Claude uses Gemini only when you ask for it, by a slash command or in plain words.
The guard hook stops Claude from calling agy directly, so every call goes through agy-call.
## How it works
A coding task runs in three lanes: Claude asks, agy-call sets up the worktree and the grant and checks every turn, and Gemini only edits files inside its worktree.
When your check fails, Gemini gets a fix turn in the same conversation; when Gemini needs a command the grant does not allow, the task stops as blocked until Claude widens the grant and continues it.
Every task, review and run job moves through these states, and the exit code tells a script which one it ended in.
A review follows the same path with a read-only snapshot instead of a worktree.
docs/diagrams/how-it-works.html has both diagrams on one page.
## Commands
| Slash command | What it does |
| /agy:task [--background] [--continue JOB] [--model M] [--effort E] | Hands a coding task to Gemini in its own worktree on branch agy/ ; Claude picks the build and test commands Gemini may run, then checks, commits and merges the result locally and never pushes. |
| /agy:review [--background] [--scope auto\|working-tree\|branch] [--base REF] | Gemini reviews the current change and returns findings marked MUST-FIX, SHOULD-FIX or NIT. |
| /agy:adversarial-review [--background] [--scope ...] [--base REF] [focus text] | The same review, told to assume the change has defects and to challenge its design. |
| /agy:status [JOB] [--all] | Lists the jobs of this repository, or shows one job in full. |
| /agy:result [JOB] | Prints a job's outcome: a task's hand-back or a review's findings. |