fix(cli): avoid encoded PowerShell commands - #11526
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Previous Review Summaries (2 snapshots, latest commit e95384d)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit e95384d)Status: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (2 files)
Fix these issues in Kilo Cloud Previous review (commit 579a787)Status: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (5 files)
Reviewed by gpt-5.4-20260305 · Input: 45.3K · Output: 5.5K · Cached: 78.3K Review guidance: REVIEW.md from base branch |
catrielmuller
approved these changes
Jun 22, 2026
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
fix(cli): avoid encoded PowerShell commands
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Windows endpoint security tools commonly treat
powershell.exe -EncodedCommand <base64>as obfuscated command execution. Kilo started using that transport to avoid Windows PowerShell mojibake, but the command-line shape is indistinguishable from a common AV and EDR heuristic even when the decoded command is benign.This keeps the Windows PowerShell UTF-8 setup from #11148 while making the executed command visible to PowerShell as plaintext via
-Command. The wrapper still sets console input, console output, and `` to UTF-8 before running the approved command, so the Unicode behavior added for localized Windows output remains in place without the nested Base64 decode andScriptBlock.Createpath.The result is a less suspicious process command line for Windows users and security tooling while preserving the intended PowerShell 5.1 and PowerShell 7 invocation shape.