live-sessions: report Kimi Code context tokens and window - #1358
Merged
Conversation
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.
The Kimi Code live row landed without a context ring because the window size was unknown. Kimi records both numbers itself: every
llm.requestcarriesmaxTokens(1,048,576 for k3) and every turn ends with atoken_counting.measuredrecord holding the current context (664,620 on this machine, which Kimi's own footer shows as 649k/1M). The collector now reads both from the tail it already scans for the model, and nulls both when either is missing so the app never draws a ring without a window.18 live-session tests pass, tsc clean, verified against the real Kimi session store.