fix(kimi-code): select compatible PowerShell for Computer Use - #2686
Conversation
🦋 Changeset detectedLatest commit: b675c91 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4632b8ebec
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3b687d753a
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. You're on a roll. Reviewed commit: ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback". |
Related Issue
No linked issue. This fixes Windows installation failures reproduced from Kimi Computer Use debug sessions and a naming mismatch observed after installation.
Problem
The Windows Kimi Computer Use installer was always launched with the system
powershell.exe. On systems where that PowerShell installation does not provide commands required by the official setup script, such asGet-FileHash, installation fails even when a compatible PowerShell 7 installation is available.The failure also happened after entering the capability installation flow, without first checking whether the selected PowerShell could run the official installer.
A runtime repair also replaced the plugin even when its wiring was already healthy. On Windows, a live plugin MCP process can keep that managed directory locked, exposing a raw
EBUSYrename error instead of actionable recovery guidance.Before installation, the Official marketplace used the built-in capability name
Kimi Computer Use. After installation, the Installed tab used the Windows plugin manifest nameKimi Computer Use for Windows, making the same product appear to change names.What changed
Kimi Computer Use for Windowsfor the Windows capability so the Official and Installed tabs display the same name.@moonshot-ai/kimi-code.Verification
pnpm --filter @moonshot-ai/agent-core-v2 exec vitest run test/app/capability/kimiCu.test.ts— 31 tests passed.pnpm exec vitest run apps/kimi-code/test/tui/commands/plugin-commands.test.ts apps/kimi-code/test/tui/commands/plugins-capability.test.ts— 13 tests passed.pnpm --filter @moonshot-ai/agent-core-v2 test— 300 test files and 4757 tests passed.pnpm --filter @moonshot-ai/agent-core-v2 typecheck— passed.pnpm --filter @moonshot-ai/agent-core-v2 lint:imports— passed.pnpm --filter @moonshot-ai/kimi-code typecheck— passed.pnpm exec oxlint --type-awareon the changed TypeScript files — passed.pnpm exec changeset status— passed.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.