Context window setting is now live, per agent tab - #24
Merged
Conversation
- Bump the MandoCode harness pin: the context window now rides on every chat request as num_ctx instead of an env var applied only when MandoCode starts the Ollama daemon, and conversations compact before the window overflows - Context window setting is now genuinely per-agent: label and caption no longer call it app-wide, and changes apply from the agent's next message - Model-switch message, ConfigCoordinator notes, README, and CHANGELOG updated
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.
Summary
Companion to the MandoCode engine PR "Send the context window with every request and compact before overflow" (DevMando/MandoCode). It picks up the engine change that makes the context window setting real in every setup, and updates the desktop app's settings screen and messages that still described the old behavior. Merge the engine PR first, then this one.
What changed
Why it matters
The desktop settings screen was promising something it couldn't deliver: users could set a context window, see a confirmation, and still be running on whatever the Ollama desktop app happened to be set to. That mismatch was the root cause of small local models failing mid-conversation with an empty response.
Scope and risk
Verification