feat: delegate issue triage to subject agents - #584
Draft
neubig wants to merge 2 commits into
Draft
Conversation
Co-authored-by: openhands <openhands@all-hands.dev>
Co-authored-by: openhands <openhands@all-hands.dev>
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
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.
Why
The existing issue-triage extension attaches its scanner to a conversation and runs the scanner inside that agent runtime. Scanning and deduplication are deterministic automation work; only the selected issue needs an agent and a Docker runtime.
Summary
Keep
github-issue-triageas a lightweight scheduled scanner. For every changed eligible issue, it submits an idempotent subject turn keyed by GitHub's immutable repository ID and the issue number. The delegated agent uses the selected profile to publish a readable triage comment, priority, andready-for-devlabel directly on GitHub.The extension no longer imports the SDK or handles Agent Server URLs, session keys, workspaces, conversations, result artifacts, or runtime lifecycle. Those responsibilities are provided once by the Automation service.
Issue Number
Closes #583
How to Test
Dependencies
This is an independent
main-based PR. Its runtime behavior requires OpenHands/automation#468. Profile-scoped credentials require OpenHands/automation#466 and OpenHands/software-agent-sdk#5046; the delegated Docker agent uses the profile/runtime boundary from OpenHands/software-agent-sdk#5017 and #3403.