Entry points now route to Kimi Code installer
This release1 featureNew capabilitiesAI-tallied from the release notesCLI entry points now short-circuit to a Kimi Code installer.
npx @buildinternet/releases get moonshotaiRecently shipped 1.52.0, whose CLI entry points now short-circuit straight into a Kimi Code installer instead of running kimi-cli itself.
The CLI's run is over. Version 1.51.0 archived the repository and points users to Kimi Code CLI. The release before it, 1.50.0, had already made the handoff explicit: the update flow recognizes the deprecation and offers a one-key migration, so existing users can switch without reconfiguring.
Reasoning and context handling tightened. Completion budget now draws on remaining context. Empty-string reasoning_content is preserved as a ThinkPart, and Kimi reasoning effort is no longer sent implicitly.
Telemetry events aligned with the TS schema. Added trace_id and previously missing events to match expected fields.
Anthropic beta header omitted when unused. kosong no longer sends the anthropic-beta header when no beta features are declared.
CLI entry points now short-circuit to a Kimi Code installer.
Introduces a deprecation-aware update flow that prompts users to migrate to Kimi Code with a single command. Also includes a fix to omit empty anthropic-beta header when no beta features are declared.
Kimi CLI no longer sends reasoning effort implicitly, and the completion budget now correctly uses remaining context. Empty-string reasoning_content is preserved as ThinkPart, and telemetry events align with the TS schema.
/clear is now an alias for /new — both commands start a new session; previously /clear only cleared context without creating a new session/h, ?, and status now resolve to their canonical commands (/help, /usage); the completer and help output display alias matches as /name (alias) for clarity/usage alias registration — the…bash.exe (POSIX semantics) instead of powershell.exe. Windows users get the same Unix-style command syntax (&&, ||, |, /dev/null, grep, sed, etc.)….zip URL — kimi plugin install now accepts HTTP(S) URLs ending in .zip (e.g. GitHub/GitLab archive links like .../archive/refs/heads/main.zip) and downloads + extracts them before resolving plugin.json, in addition…--yolo mode unintentionally preventing the model from calling AskUserQuestion — yolo used to inject a system reminder telling the model it was in "non-interactive mode" and must not ask, and the ask-user tool auto-dismissed in yolo. Both were wrong: yolo only…### Project / ### User / ### Extra / ### Built-in headings so the model can tell where each skill came from, and…Rejected by user misleading message when an approval modal times out — after the 300s safety timeout, the tool call now rejects with Rejected: approval timed out, so users returning to their session after stepping away can tell the rejection was a timeout rather…--print mode, the process now waits for running background agents to finish and lets the model process their results, instead of exiting and killing them. The wait is capped at `min(max(active_task.timeout_s or…invalid_request_error — Opus 4.7 (which rejects the legacy {type: "enabled", budget_tokens: N} thinking config) now correctly uses adaptive thinking, and the client explicitly sets display: "summarized" so thinking content still…show_thinking_stream default to true so fresh installs see the streaming reasoning preview out of the box; set it to false in your config to keep the compact 1.32 indicatorTaskStop — stopping a stuck background agent no longer prints Unhandled exception in event loop / Exception None and freezes the terminal; the cancelled task is now kept in the manager's live-tasks dict until its runner finishes cleaning up,…kimi-k2.5 version references from the welcome screen and /login tip