v1.42.0
- Shell: Switch the Windows shell backend from PowerShell to Git Bash, so the Shell tool now runs commands through
bash.exe(POSIX semantics) instead ofpowershell.exe. Windows users get the same Unix-style command syntax (&&,||,|,/dev/null,grep,sed, etc.) as Linux/macOS. Requires Git for Windows installed: kimi-cli locatesbash.exevia theKIMI_CLI_GIT_BASH_PATHenv override →where.exe git→ standard install paths (C:\Program Files\Git\bin\bash.exe); if none resolve, kimi-cli prints an install hint and exits at startup - Shell: Defend against hallucinated CMD-style
2>nulredirects on Windows by rewriting them to2>/dev/nullbefore reaching git-bash — without this defense git-bash would create a file literally namednul(a Windows reserved device name) that breaksgit add .andgit clone; on Linux/macOS,>nulis a legitimate redirect to a file namednuland is left untouched - File: Accept POSIX-form paths on Windows in
ReadFile,WriteFile,StrReplaceFile,Glob, andGrep— these tools now recognize/c/Users/foo(Git Bash style),/cygdrive/c/Users/foo(Cygwin style), and\\server\share(UNC) in addition to native Windows paths, automatically converting to native form for filesystem operations - Shell: Clear partial streamed output when an LLM step is retried — previously, if a step failed mid-stream (e.g. rate limit or server error), the incomplete text and unfinished tool-call blocks from the aborted attempt would remain on screen and be mixed with the new attempt's output. The shell UI now discards the partial state and prints a retry banner showing the reason, attempt count, and wait time; print mode also discards buffered assistant messages on retry
- Wire: Bump protocol version to 1.10 — add
StepRetryevent emitted when a step attempt fails and will be retried, carrying attempt count, wait time, and error details - Core: Stop plan-mode and afk-mode workflow prompts from being injected into subagents — subagents share session-level mode state for persistence, but their YAMLs typically exclude root workflow tools such as
EnterPlanMode,ExitPlanMode, andAskUserQuestion. These prompt injections are now root-only. Tool-level read-only checks under plan mode are unchanged, so behavior compatibility is preserved
Fetched June 4, 2026


