Kimi Code

The Kimi Code CLI exposes a full hook surface, so context-mode integrates through TOML-declared hooks plus an MCP server. Together they keep the bulk of raw payload bytes out of your window by routing data-heavy output into the sandbox and answering from the FTS5 knowledge base.

context-mode registers seven hooks on Kimi Code. The wire protocol is JSON stdin/stdout, the same one Codex CLI uses.

• PreToolUse
• PostToolUse
• SessionStart
• SessionEnd
• PreCompact
• UserPromptSubmit
• Stop

Install

Kimi Code has no plugin marketplace, so install the package globally first, then declare the hooks and register the server. Hooks live in ~/.kimi-code/config.toml (TOML) and the MCP server is registered in ~/.kimi-code/mcp.json (JSON).

node --version

npm install -g context-mode

{
  "mcpServers": {
    "context-mode": {
      "command": "context-mode",
      "args": []
    }
  }
}

[[hooks]]
event = "PreToolUse"
matcher = "Bash|Shell|Read|Edit|Write|WebFetch|Agent|ctx_execute|ctx_execute_file|ctx_batch_execute|ctx_fetch_and_index|ctx_search|ctx_index|mcp__"
command = "context-mode hook kimi pretooluse"
timeout = 30

[[hooks]]
event = "PostToolUse"
command = "context-mode hook kimi posttooluse"
timeout = 30

[[hooks]]
event = "SessionStart"
command = "context-mode hook kimi sessionstart"
timeout = 30

[[hooks]]
event = "SessionEnd"
command = "context-mode hook kimi sessionend"
timeout = 30

[[hooks]]
event = "PreCompact"
command = "context-mode hook kimi precompact"
timeout = 30

[[hooks]]
event = "UserPromptSubmit"
command = "context-mode hook kimi userpromptsubmit"
timeout = 30

[[hooks]]
event = "Stop"
command = "context-mode hook kimi stop"
timeout = 30

cp "$(npm root -g)/context-mode/configs/codex/AGENTS.md" ./AGENTS.md

CM_ROOT="$(npm root -g)/context-mode"; cp "$CM_ROOT/configs/codex/AGENTS.md" ~/.kimi-code/AGENTS.md

How detection works

context-mode identifies Kimi Code from its config directory and resolves everything relative to that root.

Set KIMI_CODE_HOME to relocate the config directory; context-mode then resolves the hooks, mcp.json, and session storage from that root instead of ~/.kimi-code/.

Verify your savings

Confirm context-mode is actually saving you tokens, not just installed:

• In a Kimi Code session, type ctx stats in chat to see the tokens saved and the context-window savings ratio for the session, plus the per-tool breakdown. Run a few data-heavy commands first so the numbers reflect real routing.

• Run context-mode doctor in your terminal to confirm the hooks and MCP server are registered. The Kimi-specific checks cover:

  • the kimi binary on your PATH
  • each [[hooks]] entry in ~/.kimi-code/config.toml
  • the context-mode entry in ~/.kimi-code/mcp.json

  The same run also reports the global checks: language runtimes and the FTS5 knowledge base.

context-mode doctor

To isolate a single hook, pipe a JSON event into the dispatcher and inspect what it writes to stdout:

echo '{}' | context-mode hook kimi pretooluse

A clean doctor run plus a climbing ctx stats savings ratio means the hooks are registered and context-mode is routing your data-heavy commands into the sandbox.

Related