signal insight

Kimi CLI v1.47.0 shifts users toward successor migration

Kimi CLI’s June 6 activity showed a clear transition pattern: low issue volume, migration-focused PRs, and a v1.47.0 release framed around moving users to a successor Kimi Code CLI. The signal is useful because graceful deprecation and migration paths are becoming part of the AI coding-tool lifecycle.

Published Jun 6, 2026 Updated Jun 8, 2026 2 sources

Moonshot AIKimi CLIai coding toolsplatform expansionlow impact

ai-coding-toolsmigrationdeveloper-toolsproduct-lifecycleagentsplatform expansion

Impact: low
Confidence: 76%
Change type: platform expansion
First seen: Jun 6, 2026
Last updated: Jun 8, 2026
Audience: developersai-coding-tool-usersdevtools-builders
Status: Ready

Summary

What changed

Kimi CLI v1.47.0 and related PR activity focused on migration and sunset behavior rather than new feature expansion.

Why it matters

AI developer tools are already entering replacement cycles. Clear migration commands, auth continuity, and successor positioning can reduce churn when a vendor or project shifts users to a new binary or product line.

Evidence excerpt

Agents Radar’s June 6 CLI digest described Kimi CLI as a transition-state project with v1.47.0 and migration-focused PRs promoting a successor Kimi Code CLI.