What feature would you like to see?
Use case: Building persistent session memory / conversation logging on top of Kimi CLI hooks.
Current state: The UserPromptSubmit hook exposes the user's message, but the Stop hook payload only contains session_id, cwd, and stop_hook_active. It does not include the assistant's response text.
Requested change: Include the assistant's final response text in the Stop hook payload, or add a new observation-only hook (e.g. AssistantResponse) that fires after the response is complete and includes the full text.
Why it matters: Without the assistant side, third-party memory systems can only log user prompts, which makes cross-session recall and fact extraction much weaker.
Additional information
No response
What feature would you like to see?
Use case: Building persistent session memory / conversation logging on top of Kimi CLI hooks.
Current state: The UserPromptSubmit hook exposes the user's message, but the Stop hook payload only contains session_id, cwd, and stop_hook_active. It does not include the assistant's response text.
Requested change: Include the assistant's final response text in the Stop hook payload, or add a new observation-only hook (e.g. AssistantResponse) that fires after the response is complete and includes the full text.
Why it matters: Without the assistant side, third-party memory systems can only log user prompts, which makes cross-session recall and fact extraction much weaker.
Additional information
No response