fix(tui): include thinking effort in status line payload - #2741
Draft
GarryCodespace wants to merge 1 commit into
Draft
fix(tui): include thinking effort in status line payload#2741GarryCodespace wants to merge 1 commit into
GarryCodespace wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: 3d15146 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 |
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
Resolve #2713
Problem
Custom status line commands receive a JSON snapshot on stdin, but that snapshot omitted the current thinking effort. The built-in footer therefore updated when the effort changed while a custom footer had no equivalent source of truth.
What changed
thinkingEffortto the custom status line payload and populate it from the current TUI state.Verification
pnpm exec vitest run apps/kimi-code/test/tui/components/chrome/footer-status-line.test.ts— 17 passedpnpm --filter @moonshot-ai/kimi-code typecheckoxlint— no new errorspnpm --filter kimi-code-docs buildChecklist
gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.