fix(cli): point curl upgrade at the install script#11601
Open
marius-kilocode wants to merge 1 commit into
Open
fix(cli): point curl upgrade at the install script#11601marius-kilocode wants to merge 1 commit into
marius-kilocode wants to merge 1 commit into
Conversation
The curl upgrade path fetched https://kilo.ai/install (the marketing landing page) and piped HTML into bash, so curl-installed CLIs never upgraded. Point it at https://kilo.ai/cli/install, the actual installer.
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (4 files)
Reviewed by gpt-5.4-20260305 · Input: 107.5K · Output: 5.1K · Cached: 373.8K Review guidance: REVIEW.md from base branch |
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
1 participant
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.
Problem
kilo upgrade(and the TUI's silent auto-upgrade) is broken for anyone who installed the CLI via the curl script. The binary is never replaced, so the version stays pinned to whatever was previously installed and users have to fall back tonpm install -g @kilocode/clito move forward.The curl upgrade path fetches an install URL and pipes the response body straight into
bashwithVERSION=<target>. The URL it uses,https://kilo.ai/install, is the marketing landing page (a ~200KB HTML document), not a shell script. Piping HTML into bash does nothing useful, so the upgrade silently no-ops.This was introduced in #11264, which replaced the upstream
https://opencode.ai/installscript URL withhttps://kilo.ai/install. The other package managers (npm, brew, scoop, choco) use separate code paths and were unaffected, which is why npm upgrades kept working.Fix
Point the curl install URL at
https://kilo.ai/cli/install, which is the actual installer script (the cloud app redirects/cli/installto the GitHubinstallscript). That script downloads thekilobinary into~/.kilo/binand already honors theVERSIONenv var the upgrade flow passes.Only the curl path is affected; the npm/brew/scoop/choco branches are unchanged.
Note: this repairs upgrades going forward. A CLI already stuck on the broken state still needs one manual bootstrap (via npm or
curl -fsSL https://kilo.ai/cli/install | bash), since the broken binary is the one running the upgrade.