Repository navigation
Add per-chat preamble selection - #698
Merged
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
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.
Adds explicit ordered preamble selections per chat so users can tailor startup context without changing workspace-wide catalog eligibility. Selections persist through chat lifecycle, inherit across forks and continuations, skip deleted entries safely with permanently retired UUID identifiers, and apply on the next ordinary input; the change also adds typed REST and WebSocket contracts, durable ledger notices and privacy handling, New Chat and in-chat configuration UI, catalog tombstones, and end-to-end coverage.