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.
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
Trajectory replay: Fix a few corner cases #6380
Trajectory replay: Fix a few corner cases #6380
Changes from all commits
7bbad2d
e1a7c46
b862c5a
5868759
553cecb
feccd5e
9b29063
aff6136
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
(not a 'review' comment, and this is cool anyway)
Just the other day, I was playing with Gemini-2.0-thinking, and it's been a lot of fun for coding-adjacent tasks! Among others, it explored a lot of
openhands
repo, tracked down every occurrence ofoh_action
and followed the execution flow up in frontend, downstream in backend, until it figured out everything about them. It makes itself mini-plans on the fly and does follow up, very cool!Anyway, so in the
server
, all those are set with source USER, but they're quite different, e.g. agent change actions, prompt confirmations, CmdRunActions (ran by user in terminal), MessageActions. I think none should be a problem, and cmd run actions are good for replay! We do want to replay those, if we want to achieve a similar state (hopefully), and of course, they'd be in context.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.
Yeah I think I did this check as a hack at the beginning - probably just to work around the wait_for_confirmation thing. It's been more and more clear that source USER events should be replayed too.