MoonshotAI / MoonshotAI/kimi-cli

Installation failed. The new Kimi Code is installed ✓ Kimi can't seem to make up her mind.

Open
#2,436 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
11.4k
Forks
1.3k
Avg merge
9h 47m
Merged PRs (30d)
2

Description

What version of Kimi Code CLI is running?

kimi-cli -V kimi, version 1.47.0

Which open platform/subscription were you using?

/login

Which model were you using?

Model: kimi-k2.6 │ │ │ │ ✨ Update: The new Kimi Code is here — rebuilt to be faster and more powerful. │ │ Run /upgrade; your config & sessions carry over.

What platform is your computer?

"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })" Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

This will install the new Kimi Code by running:
irm https://code.kimi.com/kimi-code/install.ps1 | iex
Your existing config & sessions will be migrated automatically.
Proceed with installation? (↑↓ navigate, Enter select, Ctrl+C cancel):

  1. Yes, install now
    2. No, just show me the command
    ==> Detected target: win32-x64
    ==> Resolving latest version from https://code.kimi.com/kimi-code/latest
    ==> Latest version: 0.11.0
    ==> Fetching manifest https://code.kimi.com/kimi-code/0.11.0/manifest.json
    ==> Downloading https://code.kimi.com/kimi-code/0.11.0/kimi-code-win32-x64.exe
    ==> Verifying checksum

ERROR: The term 'Get-FileHash' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Installation failed.
Press Enter to exit:

The new Kimi Code is installed ✓ Your config & sessions were migrated automatically.
Open a new terminal and run kimi to start it.
(Verify with where kimi — it should point inside ~/.kimi-code.)

What steps can reproduce the bug?

Download and try to log in.
Then try to upgrade/update

What is the expected behavior?

It Shouldn't throw errors

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the upgrade flow on Windows using kimi-cli 1.47.0, then inspect the installer entry point at https://code.kimi.com/kimi-code/install.ps1 and its checksum-verification step. Confirm the behavior on the reported Windows x64 environment and ensure installation completes without the Get-FileHash error.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, python
Domain
cli, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.