feat(kimi-code): support Kimi Computer Use on Windows - #2652
Merged
Conversation
commit: |
Merged
5 tasks
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.
Related Issue
No linked issue. The official Windows x64 Kimi Computer Use plugin and runtime are available, but the built-in CLI capability was still limited to macOS.
Problem
Windows users could not discover or install Kimi Computer Use from the Official tab. The capability also needs to distinguish its stable product ID from the platform-specific backing plugin ID so installation, updates, removal guidance, and marketplace counts stay consistent.
What changed
kimi-cucapability while selecting the macOS or Windows x64 backing plugin and runtime flow by platform.doctor.Validation
pnpm --filter @moonshot-ai/agent-core-v2 exec vitest run test/app/capability/kimiCu.test.ts(26 tests)pnpm --filter @moonshot-ai/kimi-code exec vitest run test/tui/components/dialogs/plugins-selector.test.ts test/tui/commands/plugins-capability.test.ts(53 tests)pnpm --filter @moonshot-ai/agent-core-v2 lint:importspnpm --filter @moonshot-ai/agent-core-v2 typecheckpnpm --filter @moonshot-ai/kimi-code typecheckpnpm --filter @moonshot-ai/klient typecheckpnpm -C docs run buildoxlint,git diff --check, andpnpm changeset status --since=origin/mainThe package-wide agent-core-v2 test script was also attempted, but the local run hit
EMFILE: too many open filesin unrelated file-watcher and plugin-manager tests; the focused capability suite above passed.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.