Openhands resolver updates a PR branch based on unresolved review comments. Inline review comments inherently localize to a specific code file. Openhands' agents don't utilize this context and spend time localizing to which file the comments apply to.
Enhancement
Perhaps the user can have an indicator that forces openhands to start making changes from a specific file? Possible solution may look like the following -
Initialize the workspace
Navigate to the directory which contains the code file
Start a code agent with context indicating that it must start work within a specific file in the current directory
Possible benefits
reliability
lowered cost
faster resolution time (especially when comments have smaller scopes)
Impact
Enables interactive/iterative coding for users. Not quite as fast as cursor but the advantage is that PR review comments are self documenting while retaining the ability to perform rapid iterations (especially if working within one specific file)
Current
Openhands resolver updates a PR branch based on unresolved review comments. Inline review comments inherently localize to a specific code file. Openhands' agents don't utilize this context and spend time localizing to which file the comments apply to.
Enhancement
Perhaps the user can have an indicator that forces openhands to start making changes from a specific file? Possible solution may look like the following -
Possible benefits
Impact
Enables interactive/iterative coding for users. Not quite as fast as cursor but the advantage is that PR review comments are self documenting while retaining the ability to perform rapid iterations (especially if working within one specific file)