Repository navigation
feat: preserve full cloud context and migrate provider policies - #625
Merged
Merged
Conversation
sosidudku1
added a commit
that referenced
this pull request
Oct 12, 2026
Brings in #621 (queued local model switching), #625 (modelMode, config v75) and #618 (compaction). Conflict resolution: - local-models-orchestrator: #621's ModelOperationQueue now owns serialization and supersession of starts, stops and selections, so the branch's startGeneration counter is dropped. setActive keeps #621's queued request; the Core engine and its signal are passed through to the chat and embedding starts. Core loads are still tracked so Stop and shutdown can cancel a non-replacing embedding start the queue would not abort; the queue signal and the Stop signal are combined. stopGeneration and captureStopGuard stay for composer route changes. chooseEngine runs through the queue so an engine change supersedes a waiting start. - daemon-lifecycle: keep both engine and healthTimeoutMs/signal options. - models start: runLocalModelsStart takes { interactive, signal }. The engine setting is an additive optional field defaulting to llama-server, so no config migration is needed after v75.
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.
Cloud providers currently inherit the context limits intended for small local models: selected instructions and tool output can be clipped, and older results can be rewritten after a reply. This change gives cloud models a full, persistent message history so later requests reuse unchanged earlier content.
modelMode: local|cloud, exact per-model overrides, and/llm model-modeswitching. Keep one policy snapshot per turn and propagate the actual provider's policy through Fusion and fallback.cloud; explicit provider/model settings and local or unknown endpoints remain intact. Manuallocalandinheritchoices survive subsequent loads.Validation:
npm test: 1,122 files passed; 13,608 tests passed, 4 skipped.npm run lint,npm run typecheck:tests,npm run imports:check,npm run docs:check, andgit diff --checkpassed. No new test-type diagnostic allowances.These are offline correctness checks; live provider cache hit rates, quality, latency and cost have not been measured. Previously clipped local history cannot be reconstructed. The existing context-compaction implementation is already in main via #618 and is not reintroduced by this PR.