kimi-delegate

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