kimi-code/apps/kimi-code
7Sageer 759f45c985 Merge branch 'main' into spine-v2
Conflict resolution notes:
- Follow main's architecture (model-as-container, agent runtime, featurized
  todo/cron/interaction/goal) and re-apply spine features onto it.
- Port agent-scope token counting additions (rawSize/latestMeasurement/
  projected estimates, AgentStatusUpdated rawContextTokens) onto the new
  session-scope ISessionTokenCountingService; adapt spine/kap-server/TUI
  facade call sites to AgentContext-keyed APIs.
- Move branch-added cron tests into the renamed test/features/cron and
  rewrite them on the agent-runtime harness (ctx.resolve(AgentCron)).
- Port the spine-flag todo reminder gate into features/todo; silence the
  reminder lazily so DI-light test hosts keep working.
- Register contextProjector in test hosts that construct context memory
  directly; make the trailing-open-tool-exchange trim compose with main's
  closeTrailingOpenToolExchange in fork.
- Restore mimeType passthrough for staged media uploads (facade uploadFile
  -> IFileService.save) so main's video/image paste pipeline works on the
  v2 facade.
- compactionFutile now latches only when the post-compaction shape still
  exceeds the effective window itself (not the 85% trigger ratio), so
  main's provider-observed-window pre-compaction can still fire.
2026-08-24 20:07:04 +08:00
..
dist-web Merge branch 'main' into spine-v2 2026-08-24 20:07:04 +08:00
scripts feat: isolate the full-text search index from the session index and the main thread (#2701) 2026-08-07 07:38:16 +08:00
src Merge branch 'main' into spine-v2 2026-08-24 20:07:04 +08:00
test Merge branch 'main' into spine-v2 2026-08-24 20:07:04 +08:00
.gitignore feat(minidb): persistent index generations and lifecycle hardening (#2604) 2026-08-04 20:38:42 +08:00
AGENTS.md Merge remote-tracking branch 'origin/main' into spine-v2 2026-08-18 19:47:56 +08:00
CHANGELOG.md ci: release packages (#3074) 2026-08-20 21:11:45 +08:00
package.json ci: release packages (#3074) 2026-08-20 21:11:45 +08:00
README.md docs: mention Windows Git Bash requirement (#419) 2026-06-04 17:04:02 +08:00
tsconfig.dev.json feat(web): introduce Kimi web app and daemon gateway (#625) 2026-06-17 20:53:46 +08:00
tsconfig.json feat(web): introduce Kimi web app and daemon gateway (#625) 2026-06-17 20:53:46 +08:00
tsdown.config.ts chore: drop #/ import array fallbacks and custom resolution plugins (#1594) 2026-07-13 16:37:35 +08:00
tsdown.dist-worker.config.ts feat: isolate the full-text search index from the session index and the main thread (#2701) 2026-08-07 07:38:16 +08:00
tsdown.native.config.ts chore: drop #/ import array fallbacks and custom resolution plugins (#1594) 2026-07-13 16:37:35 +08:00
tsdown.worker.config.ts feat: isolate the full-text search index from the session index and the main thread (#2701) 2026-08-07 07:38:16 +08:00
vitest.config.ts chore: use raw query imports for prompt sources (#682) 2026-06-12 11:47:44 +08:00

@moonshot-ai/kimi-code

The Starting Point for Next-Gen Agents

npm License Docs

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

The recommended install path is the official script. It does not require Node.js to be installed first.

  • macOS / 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_PATH to the absolute path of bash.exe.

Then run it with a new Terminal session:

kimi --version

Alternative: npm

If you prefer npm, use Node.js 22.19.0 or later:

npm install -g @moonshot-ai/kimi-code

Or with pnpm:

pnpm add -g @moonshot-ai/kimi-code

For upgrade and uninstall instructions, see the Getting Started guide.

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 Kimi Platform API key. After login, try a first task:

Take a look at this project and explain the main directories.

Key Features

  • Single-binary distribution. Install with one command — no Node.js setup, no PATH gymnastics, no global module conflicts.
  • Blazing-fast startup. The TUI is ready in milliseconds, so opening a session never feels heavy.
  • Polished TUI. A carefully tuned interface designed for long, focused agent sessions.
  • Video input. Drop a screen recording or demo clip into the chat — let the agent watch instead of typing out what's hard to describe in words.
  • AI-native MCP configuration. Add, edit, and authenticate Model Context Protocol servers conversationally via /mcp-config — no hand-editing JSON.
  • Subagents for focused, parallel work. Dispatch built-in coder, explore, and plan subagents in isolated context windows; the main conversation stays clean.
  • Lifecycle hooks. Run local commands at key points — gate risky tool calls, audit decisions, fire desktop notifications, wire into your own automation.

Documentation

Repository & Issues

License

MIT