Kimi Code
Install, authenticate, and resume Moonshot AI's Kimi Code CLI inside Daintree, including the rolling --continue resume and the KIMI_API_KEY auth probe.
Kimi Code
Kimi Code is Moonshot AI's coding agent. It runs as a process in its own Daintree terminal panel with full PTY emulation, like every other built-in agent.
| Command | kimi |
|---|---|
| Shortcut | — (assignable in Keyboard settings) |
| Rendering | Alt-screen — Kimi draws its own full-screen TUI |
| Resume | kimi --continue (rolling history, no session ID) |
| Quit command | /exit |
| Permission bypass | --yolo |
| Platforms | macOS, Windows, Linux |
Install & Authenticate
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bashirm https://code.kimi.com/kimi-code/install.ps1 | iexInstall Git for Windows before first launch — Kimi Code uses the bundled Git Bash as its shell environment.
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bashRun /login inside the session on first launch and pick either Kimi Code OAuth or a Moonshot AI Open Platform API key. Daintree's auth probe looks for ~/.kimi/config.toml, ~/.kimi/credentials/kimi-code.json, or the KIMI_API_KEY environment variable.
uv tool install kimi-cli, Python 3.12+). Moonshot is winding that project down in favor of Kimi Code CLI, which migrates its config and sessions on install. Either one provides the kimi binary Daintree launches.KIMI_API_KEY counts as positive proof of Kimi authentication. Kimi can also be pointed at OpenAI-compatible providers, but treating OPENAI_API_KEY as a signal would wrongly mark every Codex user as Kimi-ready, so it's deliberately left out of the probe.Resuming Sessions
Kimi uses rolling history rather than a session ID: Daintree captures nothing on shutdown and resumes by relaunching kimi --continue, which reopens whatever conversation Kimi itself considers most recent. You can't choose which past conversation to return to, and because no absolute path is recorded on Daintree's side, resuming after a project move isn't confirmed to land on the right thread. Quit with /exit. See Session Management for what Daintree preserves regardless.
Launch flags, custom presets and display titles are covered in Agent Presets. What the working, waiting and exited badges on a running agent mean is covered in Agent States.
kimi isn't detected after install, confirm it's on your PATH (which kimi on macOS/Linux, where kimi on Windows), then restart Daintree.