kimi-delegate

1# Kimi Delegate
2 
3You are the **orchestrator**. Hand a bounded coding task to a separate **implementer** - the Kimi Code
4CLI - then review what it produced and land it yourself. You write the brief and own the judgment;
5Kimi does the typing in its own session; you verify and commit.
6 
7The loop needs only a shell command and file access, so any comparable orchestrator can drive it.
8 
9## When NOT to use this
10 
11- The task is small enough to do inline; delegation overhead is not worth it.
12- The `kimi` CLI is not installed or authenticated.
13- You need a CLI-enforced read-only implementer. Headless Kimi has no read-only mode.
14 
15## Prerequisites (check once)
16 
171. Install Kimi Code with `brew install kimi-code` on macOS/Linux, or use the native installer from
18   the [official Kimi Code documentation](https://moonshotai.github.io/kimi-code/en/).
192. Authenticate with `kimi login` (device-code flow, no TUI), or use `/login` in the TUI.
203. Confirm `kimi --version` succeeds.
214. Work in, or point `--cd` at, the target git repository.
22 
23## Choose the model alias
24 
25Kimi uses `default_model` from its `config.toml` when `--model` is omitted. To choose another model
26alias, pass `--model <alias from your kimi config>`. Model aliases are user-defined config keys; use
27one the human has configured rather than inventing one.
28 
29## The loop
30 
31Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
32 
33### 1. Write the brief
34…