Improve message reconciliation - #231
Open
renal128 wants to merge 3 commits into
Open
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 22791f0. Configure here.
renal128
force-pushed
the
message-reconciliation
branch
from
August 22, 2026 15:06
22791f0 to
a86df21
Compare
Co-authored-by: Cursor <cursoragent@cursor.com>
renal128
force-pushed
the
message-reconciliation
branch
from
August 22, 2026 15:40
a86df21 to
ae071f1
Compare
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
4 tasks
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
Turns out that event_id is not a unique ID - there can be multiple agent responses with the same event_id (e.g. if theres agent utterance, tool call and another agent utterance in the same turn). So we didn't have a good way to match streamed events. Recently we added responseId in the backend as unique identifiers of agent utterances, so we can match them properly, which is the focus of this PR:
response_id(one turn can produce several agent messages).messageswithchatHistory: a mixed, stable list of messages and tool calls, that can be extended with other types of entries in the future.Test plan