> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mossx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Kimi

> Detect and use local kimi. The plugin only detects. It does not install for you.

Kimi uses local `kimi`. Credentials and models stay in Kimi’s own config (usually `~/.kimi-code/`).

Open **Settings → Provider management → CLI** and confirm Kimi CLI shows **Installed**. The plugin **does not** install it for you, and it does not edit `config.toml`.

<img src="https://mintcdn.com/mossx-docs/kz4nt5KFSKzkAZwe/images/jetbrains/provider-cli.png?fit=max&auto=format&n=kz4nt5KFSKzkAZwe&q=85&s=eab9bf7003e5c4031402aa29cfb17c5a" alt="CLI detection page" width="100%" data-path="images/jetbrains/provider-cli.png" />

## Install

macOS / Linux:

```bash theme={null}
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash
kimi --version
```

Windows PowerShell:

```powershell theme={null}
irm https://code.kimi.com/kimi-code/install.ps1 | iex
```

Alternative:

```bash theme={null}
npm install -g @moonshot-ai/kimi-code
```

Docs: [MoonshotAI/kimi-code](https://github.com/MoonshotAI/kimi-code)

After install, go back to the CLI page and click **Detect again**. If the command is not found, set `KIMI_BIN` / `KIMI_PATH` / `KIMI_CLI_PATH` / `KIMI_CODE_BIN`, or add `~/.kimi-code/bin` to the system `PATH`.

## Capability differences

Compared with Claude Code:

* No plan mode
* MCP / Skills / some Settings pages are centered on Claude Code
* Stop ends the `kimi` child process
* History is isolated by runtime
* Prompt enhancer and Commit AI can use a one-shot CLI question

## If detection fails

See [Detect and install](/en/jetbrains/providers/cli).

## Next steps

* [Provider overview](/en/jetbrains/providers/overview)
* [Send the first message](/en/jetbrains/start/first-task)