- TypeScript 87%
- JavaScript 12.8%
- C 0.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
* feat: notify the agent of external changes after /reload * refactor: route watch-based AGENTS.md change alerts through the change notifier * test: pin the missed detection of trailing AGENTS.md content deletions * fix(agent-core-v2): anchor change-notifier comparisons to delivered beliefs * fix(agent-core-v2): diff the full subagent model pool in change notifications * fix(agent-core-v2): mute stale-session auto notifications during session reload * chore(agent-core-v2): regenerate manifests and complete notifier stubs for the reload fixes * chore: update the reload-change-reminders changeset * test(agent-core-v2): cover the announced-then-deleted AGENTS.md sequence * fix(vis): cover the changeNotifier.snapshot wire record * fix(agent-core-v2): harden change-notifier beliefs for legacy wires and edge baselines * fix(agent-core-v2): unmute the stale notifier when a session reload fails midway * fix(agent-core-v2): seed change-notifier beliefs from the rendered snapshot * fix(agent-core-v2): await the change-notifier snapshot dispatch * fix(vis): harden the change-notifier snapshot renderer for legacy records * test: isolate the reload e2e from the watch channel and tighten seed assertions * chore(agent-core-v2): regenerate the wire manifest for optional belief fields * chore: drop the changeset for reload change reminders * fix(agent-core-v2): diff reload reminders against persisted beliefs first * fix(agent-core-v2): recompute the bound subagent allowlist on catalog changes * fix(agent-core-v2): roll back change-notifier beliefs on conversation undo * feat(agent-core-v2): inline added profile metadata in subagent change reminders * fix(agent-core-v2): detect legacy AGENTS.md truncation and gate skill reminders * fix(agent-core-v2): reset change-notifier beliefs on context clear * feat(kap-server): project the reload session action into the OpenAPI document * fix(node-sdk): keep plugin-only reloads from refreshing workspace catalogs * fix(agent-core-v2): gate and filter subagent change reminders * fix(agent-core-v2): evaluate reminder gates against the persisted binding * fix(kap-server): scope reload catalog refreshes to the target workspace * fix(node-sdk): scope reload catalog refreshes to the target workspace * fix(agent-core-v2): reset change-notifier beliefs on compaction * fix(agent-core-v2): hash AGENTS.md files from one atomic snapshot * fix(agent-core-v2): close first-watch and legacy gaps in change detection * fix(kap-server): block reload during compaction and reconcile after failed reload * fix(node-sdk): block reload during compaction and reconcile after failed reload |
||
| .agents/skills | ||
| .changeset | ||
| .github | ||
| .husky | ||
| apps | ||
| build | ||
| docs | ||
| packages | ||
| plugins | ||
| scripts | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .oxfmtrc.json | ||
| .oxlintrc.json | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| CONTRIBUTING.md | ||
| CONTRIBUTING.zh-CN.md | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE | ||
| Makefile | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| README.md | ||
| README.zh-CN.md | ||
| SECURITY.md | ||
| tsconfig.json | ||
| vitest.config.ts | ||
Kimi Code CLI
Documentation · Issues · 中文
What is Kimi Code CLI
Kimi Code CLI is an AI coding agent that runs in your terminal — it can read and edit code, run shell commands, search files, fetch web pages, and choose the next step based on the feedback it receives. It works out of the box with Moonshot AI’s Kimi models and can also be configured to use other compatible providers.
Install
Install with the official script. No Node.js required.
- macOS or Linux:
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash
- Windows (PowerShell):
irm https://code.kimi.com/kimi-code/install.ps1 | iex
On Windows, install Git for Windows before first launch because Kimi Code CLI uses the bundled Git Bash as its shell environment. If Git Bash is installed in a custom location, set
KIMI_SHELL_PATHto the absolute path ofbash.exe.
Then, run it with a new shell session:
kimi --version
For npm install, upgrade, uninstall, see Getting Started.
Quick Start
Open a project and start the interactive UI:
cd your-project
kimi
On first launch, run /login inside Kimi Code CLI and choose either Kimi Code OAuth or a Moonshot AI Open Platform API key. After login, try your first task:
Take a look at this project and explain its main directories.
Key Features
- Single-binary distribution. Install with one command: no Node.js setup, PATH gymnastics, or global module conflicts.
- Blazing-fast startup. The TUI is ready in milliseconds, so starting a session never feels heavy.
- Purpose-built TUI. A carefully tuned interface, optimized end to end for long, focused agent sessions.
- Video input. Drop a screen recording or demo clip into the chat and let the agent watch what is hard to describe in words — turn a reference clip into a LUT, a long video into a short, a screen recording into working code, and more.
- AI-native MCP configuration. Add, edit, and authenticate Model Context Protocol servers conversationally with
/mcp-config, without hand-editing JSON. - Rich plugin ecosystem. Install skills, MCP servers, and data sources from the marketplace or any GitHub repo, with each install's trust level surfaced up front.
- Subagents for focused, parallel work. Dispatch built-in
coder,explore, andplansubagents in isolated contexts while keeping the main conversation clean. - Lifecycle hooks. Run local commands at key points to gate risky tool calls, audit decisions, trigger desktop notifications, or connect to your own automation.
- Editor & IDE integration (ACP). Drive a Kimi Code CLI session straight from Zed, JetBrains, or any Agent Client Protocol client with
kimi acp.
Use it in your editor (ACP)
Kimi Code CLI speaks the Agent Client Protocol, so ACP-compatible editors and IDEs (Zed, JetBrains, …) can drive a session over stdio. Log in once, then point your editor at the kimi acp subcommand — no extra login needed.
For Zed, add this to ~/.config/zed/settings.json:
{
"agent_servers": {
"Kimi Code CLI": {
"type": "custom",
"command": "kimi",
"args": ["acp"],
"env": {}
}
}
}
Then open a new conversation in Zed's Agent panel. See Using in IDEs for JetBrains setup and troubleshooting, and the kimi acp reference for the full capability matrix.
Docs
- Getting Started
- Interaction and approvals
- Sessions
- Using in IDEs (ACP)
- Configuration
- Command reference
Develop
Requirements: Node.js ≥ 24.15.0, pnpm 10.33.0.
git clone https://github.com/MoonshotAI/kimi-code.git
cd kimi-code
pnpm install
pnpm dev:cli # run the CLI in dev mode
pnpm test # run tests
pnpm typecheck # TypeScript check
pnpm lint # oxlint
pnpm build # build all packages
See CONTRIBUTING.md for the full contribution guide.
Community
- Issues
- For security vulnerabilities, see SECURITY.md.
Acknowledgements
Our TUI is built on top of pi-tui. We thank the authors of pi-tui for their valuable work.
License
Released under the MIT License.
