fix: strip orphaned tool_result messages after conversation truncation#416
Merged
yaojin3616 merged 1 commit intodataelement:mainfrom Apr 16, 2026
Merged
Conversation
1 task
This was referenced Apr 27, 2026
Closed
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
tool_resultblocks in the conversation history sent to the Anthropic API.ctx_size, strip any leadingrole="tool"messages whose correspondingassistant(tool_use) message was cut off by the truncation boundary.Closes #415
Root Cause
Each
tool_callDB record expands into 2 messages (assistant + tool) during history reconstruction, soconversation[-ctx_size:]can split a pair — keeping the tool result but dropping the tool use. The Anthropic API requires everytool_resultto have a matchingtool_usein the preceding assistant message.Test plan
context_window_size = 100