Repository navigation
fix(run_context): retain tool identity in checkpoint text - #114
Merged
Merged
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.
Text-format run contexts omit tool-call names and arguments while retaining anonymous result text. Checkpoint summaries therefore lose which invocation produces a result, and subsequent model turns can repeat completed work.
Preserve the function name, call ID and arguments in call text, and the matching identity beside result text. Structured prompt messages retain their existing shape. JSON encoding failures propagate to the caller.
Validation: the new contract regression fails before the change on SQLite and PostgreSQL; all 28 run-context tests pass on both engines after the change.