agent-intern
Give Claude Code an intern.
Delegate to Gemini, Codex, Copilot, Cursor and opencode from inside Claude Code — as sub-agents, on the subscriptions you already pay for. Text answers, image generation, real repo work, parallel swarms.
Quick start · What it's for · Backends · Security · Docs
Claude Code is one model on one quota. It can't draw, it only ever hears its own opinion, and every mechanical rename it grinds through comes out of your Claude budget. Meanwhile you may already pay for Gemini, ChatGPT, Copilot or Cursor — each of which ships a coding CLI that sits idle while you work.
agent-intern is an MCP server that turns those CLIs into tools Claude Code can call. Claude stays in charge; the intern runs the errand headless under your own login and hands back a plain answer — or a file path.
Quick start
1. Register the server (needs uv):
claude mcp add -s user agent-intern -- uvx agent-intern
2. Install at least one backend CLI and sign in once. Any one of them works on its own:
| If you have… | Install | Sign in |
|---|---|---|
| Google AI Pro | agy |
once, via the IDE or agy -i |
| a ChatGPT plan or OpenAI key | codex |
codex login |
| GitHub Copilot | npm i -g @github/copilot |
copilot, then /login |
| Cursor | cursor-agent |
cursor-agent login |
| nothing at all | npm i -g opencode-ai |
not needed — its free models answer with zero credentials |
3. Restart Claude Code and just ask. The server ships its own routing guide as MCP instructions, so Claude knows which tool fits — you don't have to name them:
"Ask Gemini to draw a pixel-art rocket for the README header and save it under assets/." "Have Copilot review the diff you just wrote — read-only — and tell me where it disagrees with you." "Summarise each of the six files in src/handlers in parallel with a swarm."
Any *_status tool (say, "run antigravity_status") checks a backend's setup without spending quota.
What it's for
| 🎨 Images, inside Claude Code | antigravity_image has Gemini draw it and returns the saved file — no extra API key, no extra tool. |
| 🧠 A second opinion | A different model family reviews what Claude just wrote. Their blind spots rarely overlap. |
| 🐝 Parallel fan-out | agent_swarm runs N tasks at once and can mix backends in a single call (~2.8× at 3 Gemini workers). |
| 💸 Cheaper grunt work | Bulk renames, boilerplate and first-pass ports burn their quota instead of Claude's tokens. |
| 🆓 No subscription? Still works | opencode's free models answer with zero credentials — slow, but free. |
| 🔌 Zero new auth | Piggybacks the CLI logins you already have. The bridge manages no keys of its own. |
Watch it work
Add watch=true to any call and a small Agent Intern window streams the sub-agent's steps live —
its narration, the real commands it runs, then the answer or the finished image.
| a text ask | antigravity_image — image inline |
 |
 |
agent_swarm(..., watch=true) — one row per worker; click a row to pop that agent into its own window.
More on watch mode and swarms →
Backends
| Backend | Best at | Sandbox | You need |
|---|---|---|---|
| 🛰️ Antigravity (Gemini) | fast, cheap answers — and the only image model | ❌ none by default · opt-in plan=True |
Google AI Pro |
| 🤖 Codex (OpenAI) | heavy reasoning, real repo edits | ✅ real OS sandbox¹ | a ChatGPT plan or API key |
| 🐙 Copilot (GitHub) | agentic coding | ⚠️ best-effort | a Copilot plan |
| ✳️ Cursor | the widest model menu — GPT, Claude, Grok, Composer | ⚠️ agent-enforced | a Cursor plan |
| 🧩 opencode | working with no subscription (free models take minutes) | ⚠️ agent-enforced, identical on every OS | nothing |
| 🧪 Grok Build (xAI) | experimental — unverified | ✅ on Linux/macOS only | SuperGrok / X Premium+ |
| 🌙 Kimi Code (Moonshot) | experimental — unverified | ❌ none | a Kimi plan |
¹ On Windows, codex 0.149.1's sandbox refuses every command — reads included — so a sandboxed Codex can't see your files there. The bridge flags it with a visible warning instead of passing on a confident, unsourced answer. Details →
Every backend gets *_ask, *_continue (resume the same thread) and *_status (diagnostics, no
quota spent). Antigravity adds antigravity_image and antigravity_image_swarm, and agent_swarm
fans out across every backend but Kimi — 24 tools in all.
Tool reference → ·
How each backend is driven →
Verified live against agy 1.1.25 · codex-cli 0.149.1 · copilot 1.0.80 · cursor-agent 2026.07.23 · opencode 1.18.29. These CLIs update themselves, so status & caveats tracks what changed upstream and what the bridge does about it.
How it works
flowchart LR
U([You]) --> CC([Claude Code])
CC -- "MCP tool call" --> B["agent-intern<br/>(MCP server)"]
B -- "headless, one-shot,<br/>your own login" --> CLI["agy · codex · copilot · cursor-agent<br/>opencode · grok · kimi"]
CLI -- "answer or file" --> B
B -- "plain text" --> CC
Each call launches the official CLI headless, reads the answer back from wherever that CLI reliably
puts it — a JSON envelope, an output file, stdout, or as a last resort the CLI's own transcript — and
returns it as plain text. *_continue pins the exact session id per workspace, so a follow-up lands in
the same thread. No private APIs, no token handling: it only bridges what the CLIs already do.
Security
Docs
- Setup & requirements — install from source, per-backend prerequisites,
*_BINoverrides - Tool reference — every tool, argument and default
- Backends in depth — answer paths, session resume, models & auth, the experimental backends
- Watch mode & swarm
- Security
- FAQ — terms of service, cost, which backend when, making Claude offer to delegate
- Status & caveats — version-by-version compatibility notes
- Changelog
Contributing
The CLIs behind this bridge update themselves, so most breakage is upstream drift rather than a bug
in the bridge. A report that includes the relevant *_status output usually pins it down in one go.
Open an issue ·
Start a discussion · Developed on Windows —
confirmations from macOS and Linux are very welcome.
Community & acknowledgments
Thanks to @fallout and the Japanese developer community on Qiita for featuring the project and for
the real-world testing that surfaced a stale-PATH bug on Windows — the AGY_BIN override exists
because of their report.
Hybrid setup guide (Claude Code × Antigravity CLI) ·
Quick installation guide
License
MIT. Do whatever you want with it.
1 maintainer
Release files for agent-intern 0.30.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| agent_intern-0.30.2.tar.gz | 139.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_intern-0.30.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 296.5 kB
Release files / agent_intern-0.30.2.tar.gz
| Download URL | agent_intern-0.30.2.tar.gz |
|---|---|
| Size | 139.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9de0d9f1253a13cbdf78341f41af444dcb4f41070c3b53c6217e2a4515fe9f03
|
|
BLAKE2b-256 checksum How to use checksums |
052aee74c0c4774a4f7e99699151c133ceee3208a36fd1cf6b82e42c8a03fc75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / agent_intern-0.30.2-py3-none-any.whl
| Download URL | agent_intern-0.30.2-py3-none-any.whl |
|---|---|
| Size | 157.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f7c688931aa2bbe17c6ff8948d25a700bc5f6c042a3576eaea9a8dca2b302f6
|
|
BLAKE2b-256 checksum How to use checksums |
ed0cf362ab4a503ab8a909cac1d57779419602b2a5f1c81eab015dade411726d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency log
