mcode-delegate

1# MiniMax Code Delegate
2 
3You are the **orchestrator**. This skill lets you hand a bounded coding task to a separate
4**implementer** — the MiniMax Code CLI (`mcode`) — then review what it produced and land it yourself.
5You write the brief and own the judgment; MiniMax Code does the typing in your working tree; you
6verify and commit.
7 
8Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell
9command and read a file, so it works the same whether you are Claude Code, OpenCode with a selected
10model, or any comparable agent. (It is designed for and run on Claude Code; treat other orchestrators
11as designed-for, not yet proven.)
12 
13## When NOT to use this
14 
15- The task is small enough to just do inline — delegation overhead is not worth it.
16- `mcode` is not installed or not signed in (run `mcode login`, or `mcode login --region global`).
17- You want to write the code yourself, or you only need a review of local changes (`mcode exec review`
18  does that directly).
19- You need writes outside the target tree to be impossible, not just unlikely. MiniMax Code has no
20  sandbox; use an OS-enforced one such as `codex-delegate`, or run this inside a container.
21 
22## Read this before the first dispatch: the autonomy model
23 
24`mcode exec` takes a permission policy — `smart`, `full`, or `off` — and has **no sandbox and no
25read-only or plan setting** for a headless run (`ask` needs the TUI or ACP).
26…