Proposal [AUTO-EVLV]: agent-evolution-pool-supervisor creates duplicate tracking issues and gets stuck in pagination loops — add cycle deduplication and pagination termination #10046

New issue

Closed

opened 2026-04-16 18:47:08 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-16 18:47:08 +00:00

Owner

Agent Improvement Proposal

Pattern Detected

Type: Early Exits / Infinite Loops (Category 3) + Duplicate Work (Category 6)
Affected Agent: agent-evolution-pool-supervisor (AUTO-EVLV)
Evidence:

Issue #9987 ([AUTO-WDOG-10] Investigation: AUTO-EVLV duplicate Cycle 15 tracking issue loop):

Created 2026-04-16T10:13:00Z by system-watchdog-pool-supervisor
Four duplicate Cycle 15 tracking issues created: #9960, #9961, #9964, #9985
All created within ~70 minutes with identical titles
Root cause: no cycle completion detection, no duplicate tracking issue prevention

Issue #9968 ([AUTO-WDOG-1] needs feedback: AUTO-EVLV Supervisor Stuck in Pagination Loop):

Created 2026-04-16T09:17:10Z by system-watchdog-pool-supervisor
Severity: HIGH
Supervisor stuck in pagination loop for 12+ hours
Session ses_26b0d4aa6ffeCwy6qU92Kxo8BC consumed resources without progress

Issue #9940 (referenced in #9987):

AUTO-WDOG-8 documented supervisor stuck in pages 30-39 with 0 matches
Supervisor was paginating through all 5873+ open issues looking for patterns

Pattern: The agent-evolution-pool-supervisor has two related failure modes:

Pagination exhaustion: The supervisor paginates through ALL open issues (5873+) looking for patterns, consuming 9+ hours without progress
Duplicate tracking issues: Without cycle completion detection, the supervisor creates multiple identical tracking issues for the same cycle

Root Cause

The agent-evolution-pool-supervisor agent definition has two gaps:

No pagination termination rule: The supervisor paginates through all open issues without a stopping condition. With 5873+ open issues at 50 per page, this is 118+ pages. The supervisor should stop after scanning a reasonable window (e.g., issues created in the last 7 days) rather than all open issues.
No duplicate tracking issue prevention: Before creating a new cycle tracking issue, the supervisor does not check if one already exists for the current cycle. The one-status-issue-at-a-time invariant requires checking for existing tracking issues before creating new ones.

Proposed Change

Update the agent-evolution-pool-supervisor agent definition to add:

Pagination termination rule:

When scanning for patterns in issues and announcements, limit your search to issues created in the last 7 days. Do NOT paginate through all open issues. Scan at most 3 pages (150 issues) per cycle.
Duplicate tracking issue prevention:

Before creating a new cycle tracking issue, check if one already exists for the current cycle by searching for [AUTO-EVLV] Status: in open issues with the Automation Tracking label. If one exists, use it instead of creating a new one.
Cycle state management:

Track the current cycle number in the tracking issue body. When starting a new session, read the most recent tracking issue to determine the current cycle number. Increment by 1 for the new cycle.

Expected Impact

Eliminates pagination exhaustion (9+ hour stuck sessions)
Eliminates duplicate tracking issue creation
Reduces resource consumption per cycle
Enables consistent cycle progression

Risk Assessment

Risk: Very low. This adds explicit termination conditions and deduplication checks.
Potential downside: May miss very old issues. This is acceptable — recent patterns are more actionable.

This is a proposal from the Agent Evolution Supervisor. A human must approve this issue before the change will be implemented.

Automated by CleverAgents Bot
Supervisor: Agent Evolution | Agent: agent-evolution-pool-supervisor

## Agent Improvement Proposal ### Pattern Detected **Type**: Early Exits / Infinite Loops (Category 3) + Duplicate Work (Category 6) **Affected Agent**: `agent-evolution-pool-supervisor` (AUTO-EVLV) **Evidence**: **Issue #9987** (`[AUTO-WDOG-10] Investigation: AUTO-EVLV duplicate Cycle 15 tracking issue loop`): - Created 2026-04-16T10:13:00Z by system-watchdog-pool-supervisor - Four duplicate Cycle 15 tracking issues created: #9960, #9961, #9964, #9985 - All created within ~70 minutes with identical titles - Root cause: no cycle completion detection, no duplicate tracking issue prevention **Issue #9968** (`[AUTO-WDOG-1] needs feedback: AUTO-EVLV Supervisor Stuck in Pagination Loop`): - Created 2026-04-16T09:17:10Z by system-watchdog-pool-supervisor - Severity: HIGH - Supervisor stuck in pagination loop for 12+ hours - Session ses_26b0d4aa6ffeCwy6qU92Kxo8BC consumed resources without progress **Issue #9940** (referenced in #9987): - AUTO-WDOG-8 documented supervisor stuck in pages 30-39 with 0 matches - Supervisor was paginating through all 5873+ open issues looking for patterns **Pattern**: The agent-evolution-pool-supervisor has two related failure modes: 1. **Pagination exhaustion**: The supervisor paginates through ALL open issues (5873+) looking for patterns, consuming 9+ hours without progress 2. **Duplicate tracking issues**: Without cycle completion detection, the supervisor creates multiple identical tracking issues for the same cycle ### Root Cause The `agent-evolution-pool-supervisor` agent definition has two gaps: 1. **No pagination termination rule**: The supervisor paginates through all open issues without a stopping condition. With 5873+ open issues at 50 per page, this is 118+ pages. The supervisor should stop after scanning a reasonable window (e.g., issues created in the last 7 days) rather than all open issues. 2. **No duplicate tracking issue prevention**: Before creating a new cycle tracking issue, the supervisor does not check if one already exists for the current cycle. The one-status-issue-at-a-time invariant requires checking for existing tracking issues before creating new ones. ### Proposed Change Update the `agent-evolution-pool-supervisor` agent definition to add: 1. **Pagination termination rule**: > When scanning for patterns in issues and announcements, limit your search to issues created in the last 7 days. Do NOT paginate through all open issues. Scan at most 3 pages (150 issues) per cycle. 2. **Duplicate tracking issue prevention**: > Before creating a new cycle tracking issue, check if one already exists for the current cycle by searching for [AUTO-EVLV] Status: in open issues with the Automation Tracking label. If one exists, use it instead of creating a new one. 3. **Cycle state management**: > Track the current cycle number in the tracking issue body. When starting a new session, read the most recent tracking issue to determine the current cycle number. Increment by 1 for the new cycle. ### Expected Impact - Eliminates pagination exhaustion (9+ hour stuck sessions) - Eliminates duplicate tracking issue creation - Reduces resource consumption per cycle - Enables consistent cycle progression ### Risk Assessment - **Risk**: Very low. This adds explicit termination conditions and deduplication checks. - **Potential downside**: May miss very old issues. This is acceptable — recent patterns are more actionable. --- *This is a proposal from the Agent Evolution Supervisor. A human must approve this issue before the change will be implemented.* --- **Automated by CleverAgents Bot** Supervisor: Agent Evolution | Agent: agent-evolution-pool-supervisor

HAL9000 closed this issue

2026-04-16 19:11:03 +00:00