docs/src/content/docs/en/configuration/agents/kimi.md
Kimi CLI is Moonshot's coding agent. In CCR it is CLI only and always uses Only opened from CCR.
Use this page to route Kimi CLI to any CCR provider or Fusion model, expose several switchable models, or run separate Kimi CLI sessions.
New to CCR? Add a provider and model first. See Add a provider and the Agent Config overview.
kimi on PATH).Kimi - Work).Kimi CLI is fixed to Only opened from CCR and CLI only, so those two fields are not editable. The fields you configure are:
| Field | How to set it | Effect |
|---|---|---|
| Agent | Choose Kimi CLI | Creates a Kimi CLI launch entry in CCR. |
| Config name | Free text, e.g. Kimi - Work | Identifies the profile. Desktop commands use ccr-app "<name>"; CLI commands use ccr "<name>". |
| Enabled | Toggle on/off | Disabled profiles are not applied and not offered as launch entries. |
| Kimi model | A provider model or Fusion model | The default model. At least one model is required. |
| Available models | One or more provider/Fusion models | Models available from Kimi's /model menu. The default model is always included. |
| Environment variables | Key/value rows | Optional advanced overrides; leave empty for normal use. |
Desktop command copied from the profile card:
ccr-app "Kimi - Work"
For CLI, run:
ccr "Kimi - Work"
Inside Kimi CLI, use /model to switch among the default and available models. Every selection stays routed through CCR's providers, routing, and Fusion.
Create separate Kimi CLI profiles when you want different default models or model sets.
ccr-app command copied from the profile card, or the CLI ccr command./model and confirm the default plus available models appear./model is empty or missing models: add at least one Available model (the default counts); confirm a provider + model is configured in CCR.kimi not found: make sure Kimi CLI is installed and available from the same shell environment used to start CCR Desktop.