feat(export): record install source and shell environment in manifest#105
Merged
Conversation
Capture how the CLI was installed (npm-global, native, etc.) and the user's terminal environment (TERM, TERM_PROGRAM, multiplexer, SHELL) so exported session archives carry richer diagnostic context.
🦋 Changeset detectedLatest commit: fcc119b The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
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 |
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
1 participant
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.
Problem
The exported session archive (
kimi export) lacks information about how the CLI was installed and what terminal environment the user is running in. This diagnostic context is valuable for triaging issues from exported sessions.What changed
Added two new optional fields to the export manifest:
installSource— records how the CLI was installed (npm-global,pnpm-global,yarn-global,bun-global,native, orunsupported), reusing the existingdetectInstallSource()logic from the update module.shellEnv— captures the user's terminal environment via standard environment variables:TERM— terminal type (e.g.xterm-256color)TERM_PROGRAM— terminal emulator (e.g.iTerm.app,Apple_Terminal,vscode)TERM_PROGRAM_VERSION— terminal versionmultiplexer— detected terminal multiplexer (tmux,screen, orzellij)SHELL— user's login shellBoth fields flow through the full chain: CLI → SDK (
ExportSessionInput) → agent-core (ExportSessionPayload) →buildExportManifest()→manifest.jsonin the ZIP.Checklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.