Detect-Target returns "win32-arm64 arm64" instead of `"win32-arm64" on ARM64 Windows

[JanDeDobbeleer]

What version of Kimi Code is running?

None

Which open platform/subscription were you using?

None

Which model were you using?

None

What platform is your computer?

Windows ARM64

What issue are you seeing?

The Detect-Target function in [file/path] returns a malformed target string of win32-arm64 arm64 on ARM64 Windows machines, instead of the expected win32-arm64.

Root Cause

The switch statement matches architecture strings case-insensitively by default, and PowerShell's switch does not stop after the first match unless a break is explicitly added to each case:

$arch = switch ($rawArch) {
    'X64'     { 'x64' }
    'X86'     { 'x86' }
    'Arm64'   { 'arm64' }
    'ARM64'   { 'arm64' }
    'AMD64'   { 'x64' }
    'IA64'    { 'ia64' }
    default   { Die "unsupported architecture: $rawArch" }
}

On an ARM64 machine, $rawArch is the literal string "ARM64", which matches both the 'Arm64' and 'ARM64' cases (case-insensitive, no break). Both blocks execute, producing the array @('arm64', 'arm64') instead of a single string. When that array is interpolated in "win32-$arch", PowerShell joins the elements with a space (via $OFS), producing win32-arm64 arm64.

Fix

Remove the redundant duplicate case and add break to every case to prevent this class of bug in general:

$arch = switch ($rawArch) {
    'X64'     { 'x64'; break }
    'X86'     { 'x86'; break }
    'ARM64'   { 'arm64'; break }
    'AMD64'   { 'x64'; break }
    'IA64'    { 'ia64'; break }
    default   { Die "unsupported architecture: $rawArch" }
}

Environment

• OS: Windows on ARM64
• PowerShell version: [fill in, e.g. 7.4.x or 5.1]

Steps to Reproduce

1. Run Detect-Target on a Windows ARM64 machine.
2. Observe the returned value is win32-arm64 arm64 instead of win32-arm64.

[wangyj124]

I investigated this against the current main branch and the live CDN script. The PowerShell behavior is reproducible, and the live https://code.kimi.com/kimi-code/install.ps1 still contains the duplicate case-insensitive Arm64 / ARM64 switch branches.

However, I could not find the editable source for that installer in this repository:

• There are no tracked PowerShell files, Detect-Target, rawArch, RuntimeInformation, or Windows architecture-environment mappings in the current tree or repository history.
• The closest internal code is the Node.js native-build target logic, which already produces ${platform}-${arch} and supports win32-arm64. It runs during native builds and is not the source of the PowerShell installer.
• apps/kimi-code/scripts/native/produce-manifest.mjs only creates the manifest.json consumed by the installers.
• The public release workflow builds/uploads native artifacts and the manifest, but does not generate or deploy install.ps1.

As a result, changing the current repository's native target logic would not fix the CDN installer, and adding a standalone Detect-Target here would not be connected to the installation flow.

Could a maintainer point to the source repository/path or publication pipeline for install.ps1? If the installer is intended to live in this repository, please clarify the expected source location and test integration so the focused fix can be submitted here.

[JanDeDobbeleer]

However, I could not find the editable source for that installer in this repository

@wangyj124 I had the same issue, looked for it in the moonshot organization but also there couldn't find it. Otherwise I could've made a PR immediately ¯_(ツ)_/¯