Hooks status in Kition 0.1.41

Lifecycle dispatch proven by the client

The type surface also names task and tool events, but the public client does not prove their complete runtime ordering, payload schema, blocking semantics, or retry behavior. Do not build a safety boundary around undocumented assumptions.

• session_started is dispatched once per renderer page lifecycle
• on_quit is sent best-effort with a keepalive request during page unload
• Hook records include a command, working directory, timeout, matcher, enabled state, and last-run result fields
• Normalized hook timeouts are clamped between 1 and 300 seconds

What not to do

• Do not create .kition/hooks.json from an old example and assume Kition will load it
• Do not assume a hook can mutate tool arguments or results
• Do not treat a hook as a replacement for shell approval, backups, or least-privilege credentials
• Do not place tokens directly in a command stored with workspace data

If hooks are provisioned in a managed runtime

Treat each hook as local code execution. Pin the command, use a narrow working directory, keep timeouts short, dry-run it with non-sensitive input, and review stdout/stderr handling before enabling it.

A managed or internal environment should document its runtime version and configuration source separately; these public Desktop docs do not promise compatibility with that private setup.