Skip to content

Fix Omniparser historical message conversion using per-screenshot mappings#706

Merged
ddupont808 merged 1 commit intotrycua:mainfrom
Fizza-Mukhtar:fix/omniparser-historical-mapping
Jan 12, 2026
Merged

Fix Omniparser historical message conversion using per-screenshot mappings#706
ddupont808 merged 1 commit intotrycua:mainfrom
Fizza-Mukhtar:fix/omniparser-historical-mapping

Conversation

@Fizza-Mukhtar
Copy link
Copy Markdown
Contributor

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

  • Correct historical message conversion
  • Improved agent reliability
  • No breaking behavior changes

fixes #694

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Jan 7, 2026

@Fizza-Mukhtar is attempting to deploy a commit to the Cua Team on Vercel.

A member of the Team first needs to authorize it.

@f-trycua
Copy link
Copy Markdown
Collaborator

f-trycua commented Jan 9, 2026

Thanks for your contribution @Fizza-Mukhtar !

@ddupont808 ddupont808 merged commit 5b31349 into trycua:main Jan 12, 2026
2 of 3 checks passed
@Fizza-Mukhtar Fizza-Mukhtar deleted the fix/omniparser-historical-mapping branch January 13, 2026 07:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Omniparser: Historical Message Conversion Uses Incorrect Single-Screenshot Mapping

3 participants