MoonshotAI / MoonshotAI/kimi-cli
Windows中的powershell7默认D盘启动,打开kimi code会找不到路径 || Powershell7 in Windows starts from the D drive by default. When opening kimi code, the path cannot be found.
Nobody has claimed this yet.
- 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?
0.33
Which open platform/subscription were you using?
/login
Which model were you using?
kimi-for-coding
What platform is your computer?
No response
What issue are you seeing?
0.33版本,我设置了powershell7的默认启动目录是D盘,不从C盘的系统盘打开。从D:打开kimi code提示下面的报错,但是从D:\code打开kimi code就没问题
unexpected] Error: ENOENT: no such file or directory, watch '/D:'
at FSWatcher. (node:internal/fs/watchers:316:19)
at watch (node:fs:2538:36)
at Object.watchNative (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:237810:54)
at SignalWatchHandle.startNativeLeg (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:237885:34)
at Timeout._onTimeout (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:237924:10)
at listOnTimeout (node:internal/timers:605:17)
at process.processTimers (node:internal/timers:541:7) {
errno: -4058,
syscall: 'watch',
code: 'ENOENT',
path: '/D:',
filename: '/D:'
}
What steps can reproduce the bug?
将powershell7的默认启动路径改为D:,之后在D:下面打开kimi code,kimi code版本是0.33
What is the expected behavior?
No response
Additional information
No response
What version of Kimi Code CLI is running?
0.33
Which open platform/subscription were you using?
/login
Which model were you using?
kimi-for-coding
What platform is your computer?
No response
What issue are you seeing?
In version 0.33, I set the default startup directory of powershell7 to be the D drive and not open it from the system disk of the C drive. Opening kimi code from D: prompts the following error message, but opening kimi code from D:\code is no problem.
unexpected] Error: ENOENT: no such file or directory, watch '/D:'
at FSWatcher. (node:internal/fs/watchers:316:19)
at watch (node:fs:2538:36)
at Object.watchNative (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:237810:54)
at SignalWatchHandle.startNativeLeg (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:237885:34)
at Timeout._onTimeout (D:\a\kimi-code\kimi-code\apps\kimi-code\dist-native\intermediates\main.cjs:237924:10)
at listOnTimeout (node:internal/timers:605:17)
at process.processTimers (node:internal/timers:541:7) {
errno: -4058,
syscall: 'watch',
code: 'ENOENT',
path: '/D:',
filename: '/D:'
}
What steps can reproduce the bug?
Change the default startup path of powershell7 to D:, and then open kimi code under D:. The kimi code version is 0.33
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by launching Kimi Code 0.33 from the D: drive in PowerShell 7, then compare it with launching from D:\code. Start from the watcher call shown in apps/kimi-code/dist-native/intermediates/main.cjs and inspect how the drive-root path becomes '/D:'. Done means the drive root opens without the ENOENT watcher error while the existing subdirectory case still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, powershell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100