Repository navigation
fix(browser): correct unmade click claims #407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
syedmustafan
wants to merge
8
commits into
existence-master:main
Choose a base branch
from
syedmustafan:agent/issue-402-manual
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+309
−0
Open
Changes from 4 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
7562685
fix(browser): correct unmade click claims
syedmustafan c762666
fix(browser): cover click claims at step limit
syedmustafan a14b47d
fix(browser): ground click corrections in context
syedmustafan 6aada6f
fix(browser): scope click evidence to each turn
syedmustafan c99d066
chore: use changelog fragment for #402
syedmustafan c8529c6
fix(browser): match historical click claims to targets
syedmustafan f06a59b
Merge branch 'main' into agent/issue-402-manual
itsskofficial 2136b49
fix(browser): select click evidence by target
syedmustafan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift
Do not use one successful click to validate every click claim.
If a turn declines a click on button A and later clicks button B, this branch accepts “I clicked button A” without a correction. It has evidence only that B was clicked. Keep the clicked target with each result and match the claim to that target before treating a successful call as proof.
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I verified the concern, but did not add target matching in this focused fix: browser_click currently records a transient snapshot ref, whereas the final natural-language claim uses a human-facing label. Matching those strings would be unreliable and could itself certify the wrong action. This PR therefore keeps its narrow contract: reconcile whether a click was attempted/succeeded, and correct absent, declined, or uncertain outcomes. Reliable semantic target matching needs snapshot-label provenance and is better handled separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@syedmustafan Thanks for clarifying. A transient snapshot ref cannot reliably match a human-facing label without snapshot-label provenance. Keeping semantic target validation separate from this focused fix is reasonable.
The multi-target concern remains valid but deferred. Would you like me to open a follow-up issue for provenance-backed target matching?
✏️ Learnings added
You are interacting with an AI system.