cc-delegate
Delegates heavy development tasks from a supervisor to an autonomous worker on a cheaper model via MCP, with isolated git worktrees and provider-agnostic support.
README
cc-delegate
Delegate heavy dev tasks from Claude Code (Opus supervisor) to an autonomous worker on a cheaper model, via MCP. The worker is provider-agnostic — any model litellm can route to works. It currently defaults to MiniMax M3, but that's just a default, not a limitation.
The supervisor stays on Anthropic; only the worker is billed on the alternate provider.
Architecture
flowchart LR
Supervisor["Claude Code supervisor<br/>(Anthropic API)"]
MCP["cc-delegate MCP server<br/>Python (uv run server/main.py), stdio<br/>4 tools: run_dev_task,<br/>get_task_status, fetch_task_result,<br/>cleanup_task"]
Worktree["Disposable git worktree<br/>branch delegate/<task_id>"]
Worker["uv run worker/worker.py<br/>deepagents loop<br/>+ implementer / tester / reviewer subagents<br/>+ rubric grader"]
Provider["Provider<br/>(litellm-routed,<br/>e.g. MiniMax M3)"]
Review["Supervisor review<br/>of patch / diff"]
Supervisor -->|"run_dev_task /<br/>get_task_status /<br/>fetch_task_result /<br/>cleanup_task"| MCP
MCP -->|"createWorktree()"| Worktree
MCP -->|"uv run worker.py"| Worker
Worker -->|"litellm completion"| Provider
Provider -->|"model response"| Worker
Worker -->|"PROGRESS: {step, node, ...}<br/>(live, flushed per step)<br/>RESULT_JSON: {status, summary,<br/>turns, cost_usd, total_tokens,<br/>rubric_status, error}"| MCP
MCP -->|"latest progress<br/>(get_task_status)"| Supervisor
Worktree -->|"git diff --cached"| MCP
MCP -->|"patch + diff"| Review
cc-delegateMCP server (server/main.py, officialmcpPython SDK, run viauv run) — exposes four tools to the supervisor over stdio:run_dev_task(start a delegated task and return atask_id),get_task_status(poll — reflects livePROGRESS:updates as the worker streams them),fetch_task_result(read the final summary, patch, files changed, cost, and tokens), andcleanup_task(tear down a finished task's worktree, branch, and persisted job file).- Job persistence — every job is mirrored to
<repo>/.cc-delegate/jobs/<task_id>.jsonon each state change, soget_task_status/fetch_task_result/cleanup_taskstill work across MCP-server restarts: the in-memory registry is rebuilt from disk on demand. - Delegate worker (
worker/worker.py) — a deepagents agent, run as a subprocess viauv run(seeserver/worker_launcher.py). UsesLocalShellBackendinvirtual_mode=Trueto keep filesystem/shell access scoped to the disposable git worktree (branchdelegate/<task_id>),SubAgents for implementer/tester/reviewer roles, andRubricMiddlewareto grade completion againstdefinition_of_done/test_commandinstead of trusting the model's own "I'm done" judgment. Each run reports realcost_usdandtotal_tokensvia a litellm success callback so the supervisor knows what the delegation actually cost, and prints a flushedPROGRESS:line per graph step soget_task_statusshows what the worker is doing without waiting for completion. - Packaged skill (
skills/delegate-heavy-dev/SKILL.md) — teaches the supervisor when and how to delegate.
We started with the worker calling @anthropic-ai/claude-agent-sdk's query() pointed at a
third-party endpoint, then tried shelling out to CLI coding agents (OpenCode, dcode) — both hit
either an unresolved Claude Code CLI headless-auth bug or a Windows/no-TTY hang in dcode's rich
terminal UI. Calling deepagents directly as a library sidesteps both: no CLI, no TTY dependency,
and it gives us real control over the loop (subagents, rubric-based convergence) instead of a
black-box CLI. See KNOWN_ISSUES.md for the Claude Agent SDK auth bug writeup.
Install
Installing the plugin itself is one command (below), but two things live outside Claude Code's
control and won't be set up for you: a model API key and uv. Neither is guaranteed just
because you have Claude Code. Go through these in order:
1. Get a worker API key. Default target is MiniMax — sign up at platform.minimax.io and generate a key. (Using a different provider instead? Skip ahead to Configuration.)
2. Install uv, if uv --version
doesn't already show it. That's the only runtime prerequisite: uv run resolves the MCP
server's and the worker's inline Python dependencies (and Python itself, if needed) on first
use — no pip install, no Node.js, no build step.
3. Set DELEGATE_API_KEY as a persistent environment variable, then restart Claude Code.
This is the step most likely to trip you up: .mcp.json's ${DELEGATE_API_KEY} only reads the
OS-level environment of the process that launched Claude Code — there's no .env file
auto-loading and no interactive prompt. Setting it in a terminal after Claude Code is already
running does nothing until you restart it from a shell that has the variable.
# Windows (PowerShell) — persists across terminals, requires restarting Claude Code after
[Environment]::SetEnvironmentVariable("DELEGATE_API_KEY", "your-key-here", "User")
# macOS/Linux — add to ~/.zshrc or ~/.bashrc, then open a new shell
export DELEGATE_API_KEY="your-key-here"
4. Install the plugin.
/plugin marketplace add EtienneLescot/cc-delegate
/plugin install cc-delegate@cc-delegate-marketplace
Or locally during development: claude --plugin-dir .
5. Verify. Run /mcp — this is the checkpoint that surfaces a missing uv/key before
you're mid-task. A SessionStart hook (hooks.json) additionally probes uv --version at the
start of every session as an earlier best-effort check; it's written in exec-form (no shell) so
it behaves the same on Windows/macOS/Linux, but a hook failure isn't guaranteed to surface as a
friendly message in the transcript — treat it as a bonus signal, not the primary one.
For maintainers
No build step. The server is plain Python (server/, stdlib + the mcp SDK declared inline in
main.py); the worker is worker/worker.py. Run the test suite with:
uv run python -m unittest discover -s server -p "test_*.py"
Verify
/mcpshould list thecc-delegateserver and its four tools./statusin the supervisor session should still showapi.anthropic.com— no worker config ever leaks into the supervisor process.- Ask the supervisor to delegate a heavy task; it should call
run_dev_task, pollget_task_status, then present the diff viafetch_task_result.
Safety
The worker's LocalShellBackend runs in virtual_mode=True, scoping filesystem and shell access
to the disposable git worktree — it never runs git push or merges (also enforced via its system
prompt). The supervisor always reviews the resulting diff before deciding whether to merge branch
delegate/<task_id>.
Configuration
The facade (preferred): the plugin configures itself through its own MCP tools, driven conversationally from Claude Code — no restart needed, changes apply to the next task:
- "Show me the provider status" →
provider_statuslists your model profiles, the default, and per-profile auth state (key reachable? OAuth token cache present?). - "Add a deepseek profile" →
set_model_profile("deepseek", "litellm:deepseek/deepseek-chat", "DEEPSEEK_API_KEY");set_default_profile/remove_model_profilemanage the menu. - "Store my key for the deepseek profile" →
store_api_key("deepseek")asks you for the key through a native Claude Code dialog (MCP elicitation, Claude Code >= 2.1.199): the secret goes straight back to the server without ever entering the model's conversation. - Per task: "delegate this on the deepseek profile" →
run_dev_task(..., profile="deepseek"). The supervisor's skill forbids it from picking a non-default profile on its own.
Profiles live in ~/.cc-delegate/config.json, facade-stored keys in
~/.cc-delegate/credentials.json. Any litellm-routable model works — see
litellm's provider list.
Legacy env path (still supported): see .env.example for
DELEGATE_API_KEY, DELEGATE_MODEL, DELEGATE_API_KEY_ENV_VAR, and the guardrails
(DELEGATE_RECURSION_LIMIT, DELEGATE_RUBRIC_MAX_ITERATIONS, DELEGATE_TIMEOUT_MS). It
applies when no profile is defined; env changes require restarting Claude Code (the
restart-trap warning in Install step 3 only concerns this path).
DELEGATE_MAX_BUDGET_USD is accepted and surfaced in cost_usd, but it is not yet enforced
mid-run: deepagents/LangGraph has no built-in budget cut-off hook, so the value is reported for
visibility rather than as a hard stop.
License
MIT for this repository's own code. See NOTICE for a note on third-party terms of use.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.