Moonshot Kimi
Use Kimi in your coding tools
Step-by-step setup for Kimi in 9 coding tools: Aider, Claude Code, Cline, Codex CLI, Continue, Goose, Kilo Code, OpenCode and Zed. Every step comes from official docs, read on .
Kimi setup guides
- Documented by AiderUse Kimi in AiderAider documents connecting to any OpenAI-compatible endpoint via OPENAI_API_BASE and OPENAI_API_KEY with an openai/ model prefix. Pointed at Kimi's documented OpenAI-compatible base URL, this runs kimi-k3.api.moonshot.ai3 steps
- Documented by KimiUse Kimi in Claude CodeMoonshot publishes a Claude Code guide. You point Claude Code at Kimi's Anthropic-compatible Messages endpoint (https://api.moonshot.ai/anthropic) through the env block in ~/.claude/settings.json, with every model tier mapped to a Kimi model id. Claude Code's own env-var reference documents ANTHROPIC_BASE_URL, ANTHROPIC_AUTH_TOKEN, the ANTHROPIC_DEFAULT_*_MODEL tiers, CLAUDE_CODE_SUBAGENT_MODEL, CLAUDE_CODE_AUTO_COMPACT_WINDOW and CLAUDE_CODE_EFFORT_LEVEL.api.moonshot.ai5 steps
- Documented by ClineUse Kimi in ClineCline has a built-in Moonshot provider. The docs give a shared flow: select Moonshot under API Provider, paste the key, choose a model. In the current Cline source the provider defaults to kimi-k3, with a Moonshot Entrypoint selector for api.moonshot.ai or api.moonshot.cn.api.moonshot.ai5 steps
- Documented by KimiUse Kimi in Codex CLIMoonshot publishes a Codex guide. Kimi natively supports the Responses API, so you add a custom model provider in ~/.codex/config.toml with wire_api = "responses" and base_url https://api.moonshot.ai/v1, and Codex reads the key from KIMI_API_KEY. Codex's own advanced-config docs document the [model_providers.<id>] mechanism (base_url, env_key, wire_api).api.moonshot.ai4 steps
- Documented by ContinueUse Kimi in ContinueContinue documents a built-in moonshot provider in config.yaml with apiKey, apiBase and model options. Its default apiBase is the China endpoint and its listed models are discontinued, so set apiBase to Kimi's international base URL and model to kimi-k3.api.moonshot.ai2 steps
- Documented by GooseUse Kimi in Goosegoose ships a built-in declarative Moonshot provider, defined in the official block/goose repo. It reads MOONSHOT_API_KEY, takes an optional MOONSHOT_BASE_URL, and lists kimi-k3 (1,048,576 context), kimi-k2.7-code, kimi-k2.7-code-highspeed and kimi-k2.6. You set it up through the documented goose configure > Configure Providers flow.api.moonshot.ai5 steps
- Documented by Kilo CodeUse Kimi in Kilo CodeKilo Code documents a built-in Moonshot provider. In VS Code you add it from Settings > Providers; in the CLI you set MOONSHOT_API_KEY and configure the moonshotai provider in kilo.json. Kimi model ids get a Kimi-tuned system prompt automatically.api.moonshot.ai4 steps
- From Kimi and OpenCode docsUse Kimi in OpenCodeBoth Moonshot and OpenCode document this. OpenCode has a built-in Moonshot AI provider: you add the key with opencode auth login (or /connect), pick Kimi K3 with /models, and set reasoning effort with /variants.api.moonshot.ai4 steps
- Documented by ZedUse Kimi in ZedZed documents custom OpenAI-compatible providers under language_models.openai_compatible in settings.json, with an API key env var generated from the provider ID. A provider ID of moonshot pointed at Kimi's documented base URL runs kimi-k3, with interleaved reasoning_content and reasoning_effort support.api.moonshot.ai3 steps
No verified Kimi guide yet for Cursor, GitHub Copilot and Roo Code. We only publish a pairing once official docs cover it.
Newsletter
New models, set up the day they ship
One email per week. New model releases, the coding tools that support them and how to wire them up.