MoonshotAI/kimi-code @moonshot-ai/kimi-code@0.32.0

@moonshot-ai/kimi-code@0.32.0

Repository: MoonshotAI/kimi-code

Tag: @moonshot-ai/kimi-code@0.32.0

Published: 2026-08-04T07:14:10Z

Prerelease: no

Release notes:

Minor Changes

• #2558 `75395f6` Thanks @sailist! - Add the TurnStarted, UserPromptQueued, TaskStarted, and SessionHeartbeat hook events, enrich hook payloads with the session title and client type, include the model and profile in SessionStart, and report SessionEnd as archive when a session is archived instead of exited. Configure the new events under [[hooks]] in config.toml.

Patch Changes

• #2416 `eaab2b6` Thanks @mangeshraut712! - Fall back to the built-in models.dev catalog snapshot when the public catalog is unreachable, so Known third-party provider import still works offline or in blocked networks.

• #2083 `bfa0080` Thanks @StaR4y! - web: Fix dark-mode monochrome controls and align the chat composer corner radius with the design system.

• #2559 `dfc55a5` Thanks @wbxl2000! - Render the "/login" already-logged-in confirmation in the success color instead of dim text, so the "Already logged in. Model configuration refreshed." message is clearly visible.

• #2572 `6ba75a1` Thanks @sailist! - Rename the [loop_control] max_retries_per_step config key to max_attempts_per_step and max_steps_per_run to max_steps_per_turn: on the v2 engine the old keys no longer take effect and a startup warning prompts the rename in config.toml. The KIMI_LOOP_MAX_RETRIES_PER_STEP env var is likewise deprecated in favor of KIMI_LOOP_MAX_ATTEMPTS_PER_STEP but keeps working with a warning.

• #2585 `c396873` Thanks @sailist! - Fix submitting answers to interactive question prompts being rejected when the model provider returns tool call IDs containing colons (some OpenAI-compatible gateways).

• #2562 `071b6a5` Thanks @sailist! - Serve v1 message history from the server layer and drop the engine-side legacy message adapter; the /api/v1 message contract is unchanged.

• #2562 `071b6a5` Thanks @sailist! - Assemble the session snapshot endpoint from the engine's services for both cold and live sessions, and remove the KIMI_SNAPSHOT_READER, KIMI_SNAPSHOT_TIMEOUT_MS, and KIMI_SNAPSHOT_CACHE_LIMIT environment knobs.

• #2563 `2118544` Thanks @sailist! - Fix the context window limit showing as 0 in session status updates when no model is bound yet or the configured model no longer resolves; the limit now falls back to the default model or is omitted when unknown.

• #2563 `2118544` Thanks @sailist! - The [token_counting] strategy now only selects the reported context size: estimated keeps provider-reported usage out of the context-size display, and measured no longer gets stuck retrying an oversized compaction request until it fails.

• #2563 `2118544` Thanks @sailist! - Add a [token_counting] config section to choose how context token counts are derived: measured+estimated (default), measured (provider usage only), or estimated (heuristic only, for providers without usage reporting). Set strategy under [token_counting] in config.toml (or KIMI_TOKEN_COUNTING_STRATEGY) to switch.