Repository navigation
Run dedupe agents in the foreground #106972
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -24,3 +24,4 @@ Notes (be sure to tell this to your agents, too): | |
| - `./scripts/gh.sh issue list --state open --limit 20` — list issues | ||
| - `./scripts/gh.sh search issues "query" --limit 10` — search for issues | ||
| - Do not use other tools, beyond `./scripts/gh.sh` and the comment script (eg. don't use other MCP servers, file edit, etc.) | ||
| - Run every agent in the foreground and wait for its result before the next step | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Another issue with issue deduplication workflow is how agents handle its logic - there are still cases when issues are closed as duplicates of each other, see #19267. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This step;
located in the file above the current change, instructs to launch parallel agents - is this possible in the environment of that workflow? |
||
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.
How often the agent backgrounding happens?
Could this be one of the reasons for the lack of duplicates listing described in #79523?