Implement User-Configurable Lifecycle Hooks System

[Verdenroz]

What feature would you like to see?

Description

Currently, Kimi Code CLI operates with a fixed lifecycle. Users cannot easily inject custom context or trigger external workflows without modifying the core codebase.

Proposal

I propose implementing a Hooks System inspired by Claude Code. This would allow users to configure scripts that trigger at specific lifecycle events (e.g., SessionStart, PreToolUse, UserPromptSubmit), enabling local extensibility without bloating the core tool.

Proposed Approach

Implement a hook system configurable via a user settings file (e.g., ~/.kimi/settings.json or project-local config).

Additional information

No response

[xxchan]

For now we have no plan to support this. What's your use case for it?

For workflow-like use cases, you may try the Agent Flow feature instead.

[Verdenroz]

Thanks! I see how Agent Flows help with complex reasoning, but I am concerned they may waste tokens on tasks that shouldn't need to be thought of.

I am looking for a way to execute deterministic commands—like auto-formatting or cleanup—without the AI needing to 'decide' to do them. A lifecycle hook (like SessionEnd) allows these tasks to run 'invisibly' at the system level. This prevents Kimi from wasting context window space and tokens on maintenance tasks that don't actually require an LLM's judgment.