Repository navigation
Allow skill synchronization without session uploads - #101
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.
Shared skill storage previously also exported complete conversations and tool results at session finalization. Add
sharing.upload_sessions: falseto disable both periodic and final uploads while keeping skill synchronization available. New setup explicitly asks before enabling uploads (default no); existing configurations retain their behavior.The guard runs before creating storage clients and prevents snapshot-triggered evolution. Bilingual docs explain that existing remote artifacts, local records and inference requests are unaffected. This mitigates #11; it does not implement redaction or access control.
Validation: 165 tests passed, 1 skipped; Ruff and diff checks passed. Six new tests cover the storage boundary, evolution trigger, configuration compatibility and continued skill pull.