Skip to content
Agentmart
Submit a tool

Agent Intern

Delegate from Claude Code to Gemini, Codex, Copilot, Cursor and opencode CLIs as sub-agents.

Connector by SinanTufekci · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 29
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/sinantufekci-agent-intern

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Delegate from Claude Code to Gemini, Codex, Copilot, Cursor and opencode CLIs as sub-agents.

Use cases: agent-orchestration

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools
9 read · 10 write · 10 delete
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Tools by what they do 29

Read from the source code; the running server may list different tools.

Read 9 · Look things up without changing anything.

  • antigravity_status
  • codex_status
  • copilot_status
  • cursor_status
  • grok_status
  • kimi_status
  • muse_status
  • opencode_status
  • swarm_presets

Write 10 · Create, change, send or run things.

  • agent_swarm
  • antigravity_ask
  • codex_ask
  • copilot_ask
  • cursor_ask
  • grok_ask
  • kimi_ask
  • muse_ask
  • opencode_ask
  • preset_swarm

Delete 10 · Delete, drop, revoke or wipe things.

  • antigravity_continue
  • antigravity_image
  • antigravity_image_swarm
  • codex_continue
  • copilot_continue
  • cursor_continue
  • grok_continue
  • kimi_continue
  • muse_continue
  • opencode_continue

Network hosts it talks to 5

  • api.github.com · found in code
  • cursor.com · found in code
  • dev.meta.ai · found in code
  • github.com · found in code
  • x.ai · found in code

Files it touches

  • /home/u/codex/.venv/bin/python
  • /opt/chrome
  • /tmp/p.txt
  • Your home directory (~)
  • ~/.gemini/antigravity-cli
  • ~/.grok
  • ~/.kimi-code
  • ~/.kimi-code/config.toml
  • ~/.local/share/opencode/auth.json
  • C:\\a.png
  • C:\\a\\b.jpg
  • C:\\a\\b.png
  • C:\\a\\b\\my-repo
  • C:\\a\\b\\repo
  • C:\\elsewhere
  • C:\\img.png
  • C:\\nowhere
  • C:\\other
  • C:\\Other
  • C:\\out\\img.png
  • C:\\p
  • C:\\proj
  • C:\\Proj
  • C:\\proj\\repo
  • C:\\Users\\x\\.local\\bin\\agy.exe
  • C:\\Users\\x\\AppData\\Local\\agy\\bin\\agy.exe
  • C:\\Users\\x\\AppData\\Local\\cursor-agent\\versions\\2026.08.11-e8db854\\index.js
  • C:\\Users\\x\\AppData\\Local\\cursor-agent\\versions\\2026.08.11-e8db854\\node.exe
  • C:\\work\\opencode\\tool.exe
  • C:\\ws
  • C:\\x\\repo
  • Any path the agent passes to its tools

Tools (29)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • agent_swarmAgent swarm (mixed Antigravity + Codex + Copilot + Cursor + …, parallel)

    Run SEVERAL tasks IN PARALLEL across ALL backends in a single swarm. Each task is its own worker and names the backend to run on, so one swarm can mix Antigravity (Gemini), Codex, Copilot, Cursor, Grok, opencode and Muse workers — they run truly concurrently (capped at `max_concurrency`) and every answer comes back in one labelled block. A worker that fails is reported in place; the others still return. SECURITY: this launches N unsandboxed agents at once — N times the prompt-injection surface of a single call (see the module SECURITY note). Only use it with trusted prompts on trusted conten…

  • antigravity_askAsk Antigravity (new conversation)

    Ask Antigravity (agy CLI, Gemini by default) a question in a NEW conversation. Uses your existing AI Pro authentication (silent-auth via Windows Credential Manager). Returns the model's final response as text. Good for fast tool-calling and short tasks; for heavier reasoning pick a bigger `model` or use the host model directly. Args: prompt: Question or instruction for Antigravity. workspace: Working directory for the conversation. Defaults to cwd. Choose an existing project dir for context-aware responses. model: Optional model slug to run this conversation on (ag…

  • antigravity_continueContinue Antigravity conversation

    Continue the Antigravity conversation rooted at this workspace. Resumes the exact conversation id recorded for `workspace` (via agy's --conversation flag), not agy's global "most recent", so it stays correct even if agy was used elsewhere in between. On agy 1.1.8+ that id is the one agy itself reported for this bridge's last run in the workspace, so a follow-up resumes THIS thread even if you have since started a separate conversation in the same folder from Antigravity's own interface. Args: prompt: Follow-up message. workspace: Working directory used by the prior conversation. Defa…

  • antigravity_imageGenerate an image with Antigravity

    Generate an image with Antigravity (Gemini image model via agy CLI). Drives agy to produce a raster image on your existing AI Pro quota, saves it, and returns the absolute file path plus its real format and byte size. The host can then read the path to view the image. agy picks the image format itself (JPEG for photo-like images, PNG for flat graphics), so the returned path's extension is corrected to match the actual bytes (a requested out.png may come back as out.jpg). Runs a normal, unsandboxed agy session — same privileges/caveats as the other tools (see the module SECURITY note). Args:…

  • antigravity_image_swarmGenerate several images in parallel

    Generate several images IN PARALLEL with Antigravity (one worker per prompt). Like antigravity_image, but runs N image generations concurrently in isolated workers (capped at `max_concurrency`). Returns one block listing each image's final path/format/size (or its error). Extensions are corrected to the real bytes, exactly like antigravity_image. Same unsandboxed privileges/caveats as antigravity_swarm. Args: prompts: One image description per parallel worker. output_paths: Where to save each image (aligned to prompts). Omit to write timestamped files in the first w…

  • antigravity_statusagy bridge diagnosticsread-only

    Report diagnostics for the agy bridge setup (spends no AI Pro quota). Reports the bridge's own version and whether a newer release is available (best-effort GitHub check; honors AGY_BRIDGE_NO_UPDATE_CHECK), then checks whether agy is on PATH (and its version/compat), how much AI Pro quota is left per model family (agy 1.1.11+ answers `/usage` in print mode for free — a family at 0% is reported as a problem, since every call against it will fail until its window resets), whether agy's state directories exist, whether the newest conversation transcript is readable, and whether the SQLite conver…

  • codex_askAsk Codex (new session)

    Ask OpenAI Codex (`codex exec`) a question or task in a NEW session. Uses your existing Codex login (ChatGPT or API key — see `codex login status`). Returns the agent's final message as text, read from codex's --output-last-message file (no stdout scraping). Codex is a capable coding agent, so this suits heavier reasoning and real code work, not just cheap tool-calling. Point `workspace` at a real project dir for context-aware answers. Args: prompt: Question or instruction for Codex. workspace: Working root for the session (`-C`). Defaults to the server cwd. sandbox: Filesystem p…

  • codex_continueContinue Codex session

    Continue the Codex session rooted at this workspace (`codex exec resume`). Resumes the exact session id captured from the last codex_ask in this workspace, falling back to the newest on-disk session whose recorded cwd matches (so it still works after a server restart). The resumed session keeps its original sandbox and model — those are chosen when you start it with codex_ask. Args: prompt: Follow-up message for the existing session. workspace: Working root used by the prior session. Defaults to the server cwd. timeout_s: Max seconds to wait for codex to complete. Default 180. …

  • codex_statusCodex bridge diagnosticsread-only

    Report diagnostics for the Codex bridge setup (spends no quota). Reports the bridge's own version and whether a newer release is available (best-effort GitHub check; honors AGY_BRIDGE_NO_UPDATE_CHECK) — the same update notice antigravity_status shows, so a Codex-only install still surfaces it — then checks whether codex is on PATH (and its version), whether you're logged in (`codex login status` — no model call, no quota), where codex stores its sessions, and how many workspace sessions are pinned this run. Use this to debug "codex not found" or auth errors before spending quota.

  • copilot_askAsk GitHub Copilot (new session)

    Ask the GitHub Copilot CLI (`copilot -p`) a question or task in a NEW session. Uses your existing Copilot login (OS credential store, or a COPILOT_GITHUB_TOKEN/GH_TOKEN/GITHUB_TOKEN env var — see `copilot_status`). Returns the agent's final message, read straight from stdout (the CLI's `-s` silent mode; no scraping). Copilot is a capable agentic coder — good for real code/repo work; point `workspace` at a project dir for context-aware answers. Args: prompt: Question or instruction for Copilot. workspace: Working root for the session (`-C`). Defaults to the server cwd. sandbox: Pe…

  • copilot_continueContinue GitHub Copilot session

    Continue the Copilot session rooted at this workspace (resumes its `--session-id`). Resumes the exact session id the bridge set on the last copilot_ask in this workspace, falling back to the newest on-disk session whose recorded cwd matches (so it still works after a server restart). Unlike codex_continue, copilot re-applies permission flags on every call, so `sandbox` takes effect here too — e.g. analyze read-only with copilot_ask, then continue with "workspace-write" to apply the fix. Args: prompt: Follow-up message for the existing session. workspace: Working root used by the prio…

  • copilot_statusCopilot bridge diagnosticsread-only

    Report diagnostics for the Copilot bridge setup (spends no quota). Reports the bridge's own version and whether a newer release is available (best-effort GitHub check; honors AGY_BRIDGE_NO_UPDATE_CHECK) — the same update notice antigravity_status shows, so a Copilot-only install still surfaces it — then checks whether copilot is on PATH (and its version), an auth hint (copilot has no `login status` command, so this is best-effort — an env token is reported when set, otherwise login via the credential store is assumed and unverified), where copilot stores session state, and how many workspace …

  • cursor_askAsk Cursor (new chat)

    Ask the Cursor CLI (`cursor-agent -p`) a question or task in a NEW chat. Uses your existing Cursor login (OS credential store, or a CURSOR_API_KEY env var — see `cursor_status`). Returns the agent's final message, read straight from stdout (no scraping). Cursor is a capable agentic coder with a wide model menu (GPT / Claude / Grok / Composer); point `workspace` at a project dir for context-aware answers. Args: prompt: Question or instruction for Cursor. workspace: Working root for the chat (`--workspace`). Defaults to the server cwd. sandbox: Permission policy (maps to cursor's m…

  • cursor_continueContinue Cursor chat

    Continue the Cursor chat rooted at this workspace (resumes its chat id). Resumes the exact chat id the bridge minted on the last cursor_ask in this workspace, falling back to the newest on-disk chat whose recorded cwd matches (so it still works after a server restart). cursor applies permission flags per invocation, so `sandbox` takes effect here too — e.g. analyze read-only with cursor_ask, then continue with "workspace-write" to apply the fix. Args: prompt: Follow-up message for the existing chat. workspace: Working root used by the prior chat. Defaults to the server cwd. sandb…

  • cursor_statusCursor bridge diagnosticsread-only

    Report diagnostics for the Cursor bridge setup (spends no quota). Reports the bridge's own version and whether a newer release is available (best-effort GitHub check; honors AGY_BRIDGE_NO_UPDATE_CHECK) — the same update notice antigravity_status shows, so a Cursor-only install still surfaces it — then checks whether cursor-agent is found (and its version), whether you're logged in (`cursor-agent status`), and where cursor stores its chats. Use this to debug "cursor not found" or auth errors before spending quota.

Show 14 more tools
  • grok_askAsk Grok Build (new session) [experimental]

    Ask Grok Build (`grok -p`) a question or task in a NEW session. EXPERIMENTAL. ⚠️ Community-verified only: this bridge has never completed an authenticated round-trip, because the author has no Grok subscription. Its flags are verified against grok 1.0.3, but the answer path is not. If it misbehaves, say so rather than working around it — and please report it. Needs a SuperGrok / X Premium+ login (`grok login`) or an XAI_API_KEY env var; run `grok_status` first to check. Returns the agent's final message, read from grok's `--output-format json` result. Point `workspace` at a project dir for c…

  • grok_continueContinue Grok Build session [experimental]

    Continue the Grok session rooted at this workspace. EXPERIMENTAL. Resumes the exact session id grok returned on the last grok_ask in this workspace (`-r <id>`), falling back to grok's own "most recent session for this cwd" (`-c`) when that in-memory pin is gone — so it still works after a server restart. grok applies permission flags per invocation, so `sandbox` takes effect here too: analyze read-only with grok_ask, then continue with "workspace-write" to apply the fix. Same experimental caveat and auth requirement as grok_ask. Args: prompt: Follow-up message for the existing session. …

  • grok_statusGrok bridge diagnosticsread-only

    Report diagnostics for the Grok Build bridge setup (spends no quota). Reports the bridge's own version and any newer release (the same update notice antigravity_status shows), then whether `grok` is found (and its version), whether you're authenticated, which models it offers, and where grok keeps its data. Auth and the model list both come from `grok models`, which answers even when logged out — so this is cheap and safe to call first. Use this to debug "grok not found" or auth errors before spending quota. This backend is EXPERIMENTAL and unverified end-to-end, so a green status here means…

  • kimi_askAsk Kimi (new session) [experimental]

    Ask Kimi Code (`kimi -p`) a question or task in a NEW session. EXPERIMENTAL. ⚠️ Community-verified only — built without a Kimi account, so no authenticated round-trip has ever run and the author cannot verify it. It won't answer until you authenticate: run `kimi login` (device-code) or put an API key in ~/.kimi-code/config.toml, then check `kimi_status`. Returns the agent's final message, read straight from stdout. Kimi Code is Moonshot's terminal coding agent (Kimi K2 family); point `workspace` at a project dir for context-aware answers. Kimi print mode has NO sandbox and auto-executes ever…

  • kimi_continueContinue Kimi session [experimental]

    Continue the Kimi session rooted at this workspace (`kimi -c`). EXPERIMENTAL. Resumes the previous Kimi session for this workspace via `-c/--continue` — Kimi scopes sessions per working directory, so there's no id to track. Errors if no prior kimi_ask ran in this workspace. Same experimental caveat and auth requirement as kimi_ask. Args: prompt: Follow-up message for the existing session. workspace: Working root used by the prior session. Defaults to the server cwd. timeout_s: Max seconds to wait for kimi to complete. Default 180.

  • kimi_statusKimi bridge diagnosticsread-only

    Report diagnostics for the Kimi bridge setup (spends no quota). EXPERIMENTAL. Reports the bridge's own version and any newer release (same update notice antigravity_status shows), then checks whether `kimi` is found (and its version), whether a provider is configured (`kimi provider list` — the auth proxy, since Kimi needs `kimi login` or an API key in config.toml), and where Kimi stores its data. This backend is unverified, so expect the auth row to say "no providers configured" until you log in.

  • muse_askAsk Muse Code (new session) [experimental]

    Ask Meta's Muse Code (`muse exec`) a question or task in a NEW session. EXPERIMENTAL. ⚠️ The real model has never answered through this bridge — the author has no Muse plan. Muse's built-in offline `echo` provider verified everything else end to end (argv, event stream, answer, session resume), so a failure here is most likely auth or the model itself. If it misbehaves, say so plainly and please report it. Needs a Muse Code plan (`muse login`) or a META_API_KEY; run `muse_status` first. Returns the agent's final message (the `run_terminal` event of `muse exec --json`). Point `workspace` at a…

  • muse_continueContinue Muse Code session [experimental]

    Continue the Muse session rooted at this workspace. EXPERIMENTAL. Resumes the exact session the last muse_ask in this workspace created (the bridge names each session itself with `--session-id`). After a server restart it falls back to muse's own record of the workspace's most recent session (`muse export --last`); with no session there at all it errors rather than silently starting a fresh one. Muse applies safety flags per run, so `sandbox` takes effect here too. Same experimental caveat and auth needs as muse_ask. Args: prompt: Follow-up message for the existing session. workspace…

  • muse_statusMuse bridge diagnosticsread-only

    Report diagnostics for the Muse Code bridge setup (spends no quota). Reports the bridge's own version and any newer release, then whether `muse` is found (and which binary the bridge runs), whether credentials are present (META_API_KEY or a `muse login`), any cached model catalog, the Windows OS sandbox state, and where muse keeps its data. Muse has no free auth probe, so a green auth row means credentials exist, not that they are still valid. This backend is EXPERIMENTAL: green here means the setup looks right, not that a real answer has ever been confirmed.

  • opencode_askAsk opencode (new session)

    Ask opencode (`opencode run`) a question or task in a NEW session. The one backend here that needs NO subscription: opencode's own free hosted models (`opencode/*-free`, see `opencode models`) answer with zero credentials configured, so this works on a machine that has never logged in to anything. Add a key with `opencode auth login` for Claude/GPT-class models. Returns the agent's final message, reconstructed from opencode's `--format json` events. Point `workspace` at a project dir for context-aware answers. ⚠️ The free models are SLOW (queue-scheduled — a one-word answer has taken minutes…

  • opencode_continueContinue opencode session

    Continue the opencode session rooted at this workspace. Resumes the exact session id opencode reported on the last opencode_ask in this workspace (`-s <id>`), falling back to opencode's own "most recent session for this directory" (`-c`) when that in-memory pin is gone — so it still works after a server restart. Session scoping is per directory (verified live: the same `-c` from a different directory starts a fresh session), so pass the same `workspace` you asked in. The permission policy applies per invocation, so `sandbox` takes effect here too: analyze read-only with opencode_ask, then con…

  • opencode_statusopencode bridge diagnosticsread-only

    Report diagnostics for the opencode bridge setup (spends no quota). Reports the bridge's own version and any newer release (same update notice antigravity_status shows), then checks whether `opencode` is found (and its version), how many provider credentials are configured, which model ids are available, and where opencode keeps its data. "0 credentials" is NOT a failure here — opencode's free `opencode/*` models still answer — so that row stays ok as long as models are listed.

  • preset_swarmPreset swarm (jury / research / red team / council)

    Run a PREDEFINED swarm: a named panel of agents from different model families, each in its own role, all working on the same material in parallel. One call instead of building agent_swarm tasks by hand, and the same panel every time, so two runs (two applications, two drafts) can be compared. Built-in presets: - jury: independent jurors score the material against a rubric. You get a score table (each criterion's mean and spread, a weighted total per juror, disagreements flagged) plus each juror's reasons. For judging an application, proposal, pitch or submission. - research: o…

  • swarm_presetsSwarm presets (list, or show one to customise)read-only

    List the predefined swarms preset_swarm can run, or show one in full. Lists each preset's kind, members (role and backend), rubric for a jury, and where it comes from. Built-ins can be replaced or extended with JSON files in ~/.agent-intern/swarms/ (every project) or <workspace>/.agent-intern/swarms/ (one project; its members run read-only and it cannot replace a built-in or user preset, because it arrives with whatever repo was cloned). Broken files are listed with the reason they were skipped. Args: name: Show this preset in full, as the JSON to save and edit. Omit to list. workspa…

Compare and alternatives

    Featured in

    Signals

    Stars
    29
    Forks
    8
    Open issues
    0
    Contributors
    1
    Weekly downloads
    276
    Last commit
    Oct 15, 2026 (13 days ago)
    Last release
    Oct 14, 2026 (14 days ago)
    Last package publish
    Oct 14, 2026 (14 days ago)

    From GitHub (fetched Oct 24, 2026) and the package registry.

    Details

    Registry name
    io.github.SinanTufekci/agent-intern
    Version
    0.33.0
    Auth
    No auth
    Packages
    pypi agent-intern
    License
    MIT
    Repository
    github.com/SinanTufekci/agent-intern
    First seen
    Oct 24, 2026
    Last checked
    Oct 24, 2026
    Source
    Official MCP Registrygithub-graphql
    Cite this page

    Agent Intern MCP server. Agent Mart. https://agentmart.dev/connectors/sinantufekci-agent-intern (last updated 2026-10-24)