agy-bridge: Claude Code delegates tasks to agy
agy-bridge
An MCP bridge: Claude Code hands heavy tasks to the Antigravity CLI and only the finished answer returns to Claude context
- 65 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- By default agy runs without permission prompts and a delegated task can change files without confirmation
- File contents and prompts go to Antigravity and its models
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/agy-bridgeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- By default agy runs without permission prompts and a delegated task can change files without confirmation
- File contents and prompts go to Antigravity and its models
This is third-party code. Review the repository files before installing.
What it does
The bridge sits between Claude Code and the agy command of the Antigravity CLI. Claude sends a task, the bridge picks a suitable model among those available in agy and returns only the answer. Large files, git history searches and web lookups never reach Claude context and save its tokens. There are six tools. analyze_files takes files over 200 lines, more than three files, logs and dumps. deep_search searches git log, diff and blame and the whole repository. web_lookup reads documentation and external references. adversarial_review critiques plans, design and code. follow_up continues a previous session by session_id without resending context. delegate takes the rest of the heavy work. On first run the bridge calls agy models, caches the list and for each tool picks the first available model from Gemini families in a preference chain. Every reply ends with a line giving the model and the session ID. Output length is capped, 50,000 characters by default.
Who it is for. Claude Code users with the Antigravity CLI installed who want to relieve context and send large file analysis to another model.
Good fit when
- A large log or dump in the repository must be analyzed without cluttering Claude context
- You need a deep search through git history, blame and all project files
- A documentation lookup needs external web search through another model
- A plan or design should be critiqued by a second model
- A previous analysis should continue with a follow-up without resending files
Not a fit when
- The Antigravity CLI is not installed or authenticated: the bridge does not work without agy
- The task is small: calling agy adds latency, a cold analyze_files start takes 40 to 50 seconds
- Code must not go to third-party models: files go to Antigravity and its models
Example request
Analyze this 20,000-line log in agy, find repeating errors and return only a short conclusion to Claude.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
AGY_SANDBOX- The value true runs agy in sandbox mode
AGY_SKIP_PERMISSIONS- True by default: agy runs without permission prompts
AGY_MAX_OUTPUT_CHARS- Output length cap, 50000 by default
Limitations
Node.js 18 or newer, an installed and authenticated Antigravity CLI and Claude Code are required. Long calls can hit the client timeout, so the README advises registering the server with claude mcp add-json and a 600000 ms timeout or setting MCP_TOOL_TIMEOUT. By default the bridge passes the --dangerously-skip-permissions flag to agy (AGY_SKIP_PERMISSIONS=true), so agy acts without permission prompts, and sandbox mode is enabled separately through AGY_SANDBOX. If agy fails, Claude by default does the work itself, and strict mode disables that.
How to disable. Run claude mcp remove agy-bridge. Delete the delegation rules added to CLAUDE.md by hand. The Antigravity CLI stays installed.
FAQ
Why use the bridge?
It moves heavy work on large files, git history and web search to another model through agy. Only the answer reaches Claude context and tokens are saved.
How is the model chosen?
On first use the bridge runs agy models and takes the first available model from the chain for the tool. You can set the model explicitly with the model parameter.
How do I continue a previous analysis?
With the follow_up tool and the session_id from the footer of the earlier reply. Context does not need resending, agy continues its conversation.
How do I limit agy rights?
AGY_SANDBOX=true starts agy with the --sandbox flag and AGY_SKIP_PERMISSIONS=false removes the permission-skipping flag that is on by default.
How does it differ from claude-to-agy?
The README compares them: instead of one generic delegate_to_agy there are six purpose-built tools, model selection, session continuity, an output cap and an optional sandbox. Installation is through npx.
Discussion
No questions or reviews yet.
Related
MCP serversA plugin that calls Antigravity CLI from inside Claude Code: quick prompts, delegated tasks and a second opinion on your diff.
A Claude Code plugin that hands bulk work to Gemini through the Antigravity CLI and leaves decisions and verification to Claude
A bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
Delegating to an intern: Google's Antigravity CLI (agy) with a fast Gemini model for Claude Code, Codex, Pi and OpenCode. Code and tasks go to Google
A plugin and skill that hand tasks to Antigravity CLI (agy) from Claude Code or Codex with its own models and context
A Rust terminal task board: every task runs in its own git worktree and tmux window while Claude Code, Codex, Gemini CLI and other agents work in parallel
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| agy-bridge: Claude Code delegates tasks to agy (this card) | no | not required | 65 | |
| agy: Antigravity CLI plugin | no | 81 | a plugin that runs the Antigravity CLI as a command, without purpose-built tools or model selection | |
| Antigravity CLI | yes | 2,790 | the Antigravity CLI itself, does not include the bridge to Claude Code |
README in short
The README explains the delegation scheme, compares the bridge with another solution, lists requirements and installation, a table of six tools with model chains, environment variables, failure behavior and timeouts.