Moonshot AI

Kimi CLI shipped a dead-end streak force-stop and plugin .zip URL installs, alongside a project rename signaling the transition to Kimi Code.

Successor branding and upgrade path added. The project was renamed to Kimi CLI in documentation, with guidance added to the shell pointing users toward the Kimi Code CLI successor. This signals an intentional product transition while keeping the current toolchain usable.

Windows shell rewritten to Git Bash. The Windows backend switched from PowerShell to Git Bash, giving Windows users POSIX semantics — &&, ||, pipes, /dev/null, grep, sed — matching Linux and macOS behavior. A defense against hallucinated CMD-style 2>nul redirects was added to prevent spurious files from being created in Git repositories.

Attention and permission modes separated. The --yolo and --afk flags were split into distinct concepts: --yolo bypasses permission approvals while the user remains present, while --afk handles away-from-keyboard sessions by auto-dismissing questions. The status bar reflects each flag independently.

Skill scoping and resolution tightened. Project-scope skills now correctly win over user-scope and built-in skills when names collide, with the system prompt grouping skills under Project, User, Extra, and Built-in headings. Single-file <name>.md skills are now accepted alongside subdirectory layouts.

Shell polish and reliability fixes. Visual spacing was restored across tool call results, content blocks, and error panels. The /clear command became an alias for /new. OAuth token rotation races under concurrent instances were resolved. MCP OAuth tokens now persist to ~/.kimi/mcp-oauth/ via FastMCP 3.2.4. Repeated-tool-call reminders escalate and force-stop on a dead-end streak. Plugins can now be installed directly from a .zip URL.