fix: preserve agent context when sending pruning notifications #43
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
When the context_pruning tool or idle pruning runs while an agent (such as 'build') is active, the notification message should be sent with the same agent context. This prevents the notification from incorrectly appearing outside the agent's message flow. The fix extracts the current agent from the last user message and passes it through the notification chain to sendIgnoredMessage, which includes it in the session.prompt call.
Tarquinen
deleted the
fix/preserve-agent-context-in-pruning-notifications
branch
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
Changes
sendMinimalNotification,sendAutoModeNotification,sendHybridNotification)session.promptcall viasendIgnoredMessage