Skip to content

Run dedupe agents in the foreground - #106972

Draft
bpasero-ant wants to merge 1 commit into
mainfrom
dedupe-foreground-agents
Draft

bpasero-ant wants to merge 1 commit into
mainfrom
dedupe-foreground-agents

Conversation

@bpasero-ant

@bpasero-ant bpasero-ant commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Some dedupe runs end after a few seconds. Claude likely starts an agent in the background and ends its turn, and the action stops at that result, so the agent is cut off.

Sets CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1 on the dedupe step, and tells the command to wait for each agent.

Not run on GitHub yet; check_workflow_hardening.py passes. We'll check the first runs after merge.


Generated by Claude Code

Co-authored-by: bpasero <bpasero@anthropic.com>
@bpasero-ant bpasero-ant self-assigned this Nov 3, 2026
@bpasero-ant
bpasero-ant enabled auto-merge November 3, 2026 14:46
- `./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

Copy link
Copy Markdown

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?

- `./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

Copy link
Copy Markdown

Choose a reason for hiding this comment

The 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.

- `./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

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step;

  1. Then, launch 5 parallel agents ...

located in the file above the current change, instructs to launch parallel agents - is this possible in the environment of that workflow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants