Fix automatic compaction dropping the newest user turn - #603
Open
elrensmin wants to merge 2 commits 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.
Motivation
_first_recent_context_indexdecides where automatic compaction starts keeping rows. Its "keep whole user turns" logic could move the boundary past the last user message, silently destroying the most recent context:[user, assistant, user, assistant]kept only the finalassistantreply, dropping the newest user prompt.[user, assistant, toolResult, toolResult]compacted the entire context including the newest turn.Summary of behavior changes
Tests / checks
tests/test_coding_session.py.Notes
_first_recent_context_indexintau_coding.session; no cross-layer changes.dev-notes/compaction-keeps-newest-user-turn.md.