feat: make compaction reserve configurable - #353
Open
injectiver wants to merge 1 commit into
Open
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.
Summary
Motivation
The current hard-coded 10,000-token reserve can be too small for large context windows and long Cursor Agent turns, allowing requests to reach the provider context limit before compaction. This change makes the safety headroom configurable while providing a more conservative default.
Testing
cargo test -p cursor-server compaction --no-fail-fasttsc --noEmittsc --noEmit -p tsconfig.node.jsonvite buildNotes
On this Windows checkout, the full server suite retains four line-ending-sensitive runtime-template failures (
prefix_stability,runtime_modes,selected_images, andtext_turn). The same failures reproduce on an unmodified v0.1.2 worktree and are unrelated to this change.