Fix Omniparser historical message conversion using per-screenshot mappings #706
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
Contributor
|
@Fizza-Mukhtar is attempting to deploy a commit to the Cua Team on Vercel. A member of the Team first needs to authorize it. |
Collaborator
|
Thanks for your contribution @Fizza-Mukhtar ! |
f-trycua
approved these changes
Jan 9, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
Omniparser previously used a single element mapping derived from the most recent
screenshot to convert all historical computer_call messages. This caused incorrect
element IDs when UI state changed over time.
Solution
This PR builds element ID mappings per screenshot and applies the most recent
prior mapping when converting each message. This preserves historical UI context
and prevents incorrect element ID assignment.
Impact
fixes #694