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: PreToolUse, PostToolUse, SessionStart, SessionEnd, PreCompact, UserPromptSubmit, and Stop. The wire protocol is JSON stdin/stdout, the same one Codex CLI uses.

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 and the MCP server is registered in ~/.kimi-code/mcp.json. If you set KIMI_CODE_HOME, both files live under that directory instead.

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 the ~/.kimi-code/ config directory (or KIMI_CODE_HOME when set). Captured sessions are stored under ~/.kimi-code/context-mode/sessions/.

Verify

Confirm the install with the doctor. It checks for the Kimi Code CLI on your PATH, the language runtimes, the FTS5 knowledge base, and each hook entry in config.toml, then reports anything that needs attention.

context-mode doctor

A clean run means every hook is registered and context-mode is ready to route your next data-heavy command.

Related