Kimi Code CLI Help
Help users with Kimi Code CLI questions by consulting documentation and source code.
Strategy
- Prefer official documentation for most questions
- Read local source when in kimi-cli project itself, or when user is developing with kimi-cli as a library (e.g., importing from
kimi_cliin their code) - Clone and explore source for complex internals not covered in docs - ask user for confirmation first
Documentation
Base URL: https://moonshotai.github.io/kimi-cli/
Fetch documentation index to find relevant pages:
https://moonshotai.github.io/kimi-cli/llms.txt
Page URL Pattern
- English:
https://moonshotai.github.io/kimi-cli/en/... - Chinese:
https://moonshotai.github.io/kimi-cli/zh/...
Topic Mapping
| Topic | Page |
|-------|------|
| Installation, first run | /en/guides/getting-started.md |
| Config files | /en/configuration/config-files.md |
| Providers, models | /en/configuration/providers.md |
| Environment variables | /en/configuration/env-vars.md |
| Slash commands | /en/reference/slash-commands.md |
| CLI flags | /en/reference/kimi-command.md |
| Keyboard shortcuts | /en/reference/keyboard.md |
| MCP | /en/customization/mcp.md |
| Agents | /en/customization/agents.md |
| Skills | /en/customization/skills.md |
| FAQ | /en/faq.md |
Source Code
Repository: https://github.com/MoonshotAI/kimi-cli
When to read source:
- In kimi-cli project directory (check
pyproject.tomlforname = "kimi-cli") - User is importing
kimi_clias a library in their project - Question about internals not covered in docs (ask user before cloning)