Agy plugin for Claude Code
Use Agy from inside Claude Code for code reviews or to delegate tasks to Agy.
This plugin is for Claude Code users who want an easy way to call Agy (the Anthropic agent CLI
running Claude and Gemini family models) from the workflow they already have. It follows the
structure of OpenAI's codex-plugin-cc, adapted to
Agy's print-mode CLI.
What You Get
/agy:review for a normal read-only Agy review/agy:adversarial-review for a steerable challenge review/agy:rescue, /agy:status, /agy:result, and /agy:cancel to delegate work and manage background jobs
Requirements
- The
agy CLI installed and on your PATH. This plugin does not install Agy for you.
- An authenticated Agy session. Sign-in is interactive: run
agy in a terminal once and complete the login flow.
- Node.js 18.18 or later
Install
Add the marketplace in Claude Code:
From GitHub (the repository is private — your gh/git credentials must have access):
/plugin marketplace add nguyenhieuec/agy-plugin-cc
Or from a local clone:
/plugin marketplace add /path/to/agy-plugin-cc
Install the plugin:
/plugin install agy@agy-cc
Reload plugins:
/reload-plugins
Then run:
/agy:setup
/agy:setup tells you whether Agy is ready. If agy is missing from your PATH, install it first
and re-run setup. If Agy is installed but not signed in, run agy interactively in a terminal to
complete the login flow — there is no non-interactive login.
After install, you should see:
- the slash commands listed below
- the
agy:agy-rescue subagent in /agents
One simple first run is:
/agy:review --background
/agy:status
/agy:result
Models
Agy bundles effort into the model label — there is no separate --effort flag. The plugin accepts
either the full label or a short alias anywhere --model is supported:
| Alias | Model label |
|---|
flash | Gemini 3.5 Flash (High) |
flash-low | Gemini 3.5 Flash (Low) |
flash-medium | Gemini 3.5 Flash (Medium) |
flash-high | Gemini 3.5 Flash (High) |
pro | Gemini 3.1 Pro (High) |
pro-low | Gemini 3.1 Pro (Low) |
pro-high | Gemini 3.1 Pro (High) |
sonnet | Claude Sonnet 4.6 (Thinking) |
opus | Claude Opus 4.6 (Thinking) |
gpt-oss | GPT-OSS 120B (Medium) |
Defaults:
- Every command defaults to
flash (Gemini 3.5 Flash (High)) unless you pass --model. The
plugin pins this explicitly rather than relying on Agy's built-in default, so behavior stays
stable even if a future Agy release changes its default model.
- Resumed rescue conversations (
--resume) keep the model they were started with; pass --model
to switch.
Usage
/agy:review
Runs a normal Agy review on your current work.
[!NOTE]
Code review especially for multi-file changes might take a while. It's generally recommended to run it in the background.
Use it when you want:
- a review of your current uncommitted changes
- a review of your branch compared to a base branch like
main
Use --base <ref> for branch review. It also supports --wait, --background, and
--model <model|alias>. It is not steerable and does not take custom focus text. Use
/agy:adversarial-review when you want to challenge a specific decision
or risk area.
Examples:
/agy:review
/agy:review --base main
/agy:review --background
/agy:review --model pro
This command is read-only and will not perform any changes. When run in the background you can use
/agy:status to check on the progress and /agy:cancel to cancel the
ongoing task.
/agy:adversarial-review
Runs a steerable review that questions the chosen implementation and design.
It can be used to pressure-test assumptions, tradeoffs, failure modes, and whether a different
approach would have been safer or simpler.
It uses the same review target selection as /agy:review, including --base <ref> for branch
review. It also supports --wait, --background, and --model. Unlike /agy:review, it can take
extra focus text after the flags. Like every command it defaults to flash (Gemini 3.5 Flash
(High)); pass --model sonnet or --model opus when you want a stronger reasoning tier for the
challenge pass.
Use it when you want:
- a review before shipping that challenges the direction, not just the code details
- review focused on design choices, tradeoffs, hidden assumptions, and alternative approaches
- pressure-testing around specific risk areas like auth, data loss, rollback, race conditions, or reliability
Examples:
