Repository navigation
Add plain-language status, /context-kit panel and own settings file - #23
Merged
Merged
Conversation
Users of any level can see and change cleanup settings without editing JSON: the footer says how full the context is and when cleanup starts, and /context-kit edits the main settings in plain words. Settings move to context-kit.json, with a schema for editors, and 0.3 settings move there automatically with the same behavior, including project settings merged over global ones.
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.
Users of any level can see and change cleanup settings without editing JSON. The footer shows how full the context is and when cleanup starts (
Context 62% · cleanup at 75%)./context-kitopens a panel with plain labels; outside the TUI it prints one summary line. Settings move tocontext-kit.json(global and trusted project), with a JSON schema for editors; developers keep every option underadvanced.0.3 settings in Pi's
settings.jsonmove automatically at the first start with the same behavior. The project file gets only what the project block changed, because 0.3 merged it over the global block. Migration waits while Pi cannot read its settings, and retries after a failed write.Verified:
npm run check246/246 on Pi 1.5.2 and Pi 1.0.3; TUI smoke tests for migration, panel save, panel save failure and revert, broken Pi settings. Release as v0.4.0 because the settings location changes.