fix(cli): set process title to kimi-code - #407
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: d254660 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: |
Merged
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; this fixes process identification for npm-launched CLI sessions.
Problem
When Kimi Code is launched through npm, the operating system can show the underlying Node process instead of a stable CLI-specific process title. That makes Activity Monitor, process searches, and monitoring scripts harder to interpret.
What changed
The CLI now defines a dedicated process-name constant and sets
process.titletokimi-codeat startup. A CLI entry test covers the startup behavior, and a patch changeset records the user-visible fix.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.Validation
pnpm exec vitest run apps/kimi-code/test/cli/main.test.ts apps/kimi-code/test/tui/kimi-tui-message-flow.test.tspnpm --filter @moonshot-ai/kimi-code typecheckgit diff --check