Kilo-Org/kilocode cli-v0.22.0 on GitHub

0.22.0

#5046 fd2029c Thanks @marius-kilocode! - Add --on-task-completed <prompt> flag to send a custom prompt to the agent when the task completes. This flag requires --auto mode and allows users to define any follow-up action (e.g., creating a PR, running tests, generating documentation). The prompt is sent to the agent after the main task completes, enabling flexible post-task automation.
#5022 2fc244c Thanks @marius-kilocode! - Add syntax highlighting to code edit diffs in the CLI. Diffs now display with language-aware syntax coloring using Shiki, making code changes easier to read. Includes support for 60+ languages, automatic language detection from file extensions, and theme-aware highlighting that works with both light and dark themes. Also increased the diff display limit from 20 to 50 lines with smart context collapsing around changes.

#4988 7253ac0 Thanks @marius-kilocode! - Fix Bedrock provider validation to support API key authentication without requiring access keys
#5064 2713d06 Thanks @marius-kilocode! - Add default autocomplete suggestions for select commands (/model select, /provider select, /tasks select, /session select)
#5066 8055f15 Thanks @marius-kilocode! - Fix CLI dispose, randomUUID, and debug UX issues
#5011 9c8bb7b Thanks @marius-kilocode! - Fix multiline paste regression where pasting text with newlines would submit after the first line
#5000 1c88a66 Thanks @marius-kilocode! - Fix empty files being created when project path contains non-Latin characters (e.g., Cyrillic, Chinese)
The CLI's write_to_file command was creating empty files when the project directory path contained non-Latin characters. This was caused by improper handling of Uint8Array content in the FileSystemAPI.writeFile method. The fix ensures proper Buffer.from() conversion before writing to the filesystem.
#5058 c9f1f6a Thanks @marius-kilocode! - Fix autocomplete for /teams select and other multi-argument commands
#4985 69a541a Thanks @marius-kilocode! - Fix Windows cmd.exe display bug with escape sequences
On Windows cmd.exe, the \x1b[3J (clear scrollback buffer) escape sequence is not properly supported and causes display artifacts like raw escape sequences appearing in the output (e.g., [\r\n\t...]).