You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
watch: no per-issue failure tracking - a permanently failing issue is re-dispatched every round forever #1713
squad watch has no notion of a work item that keeps failing. An issue that an agent cannot complete is re-selected and re-dispatched on every round, indefinitely, with no escalation and no backoff.
Evidence
The only failure counter in the watch path is the circuit breaker, and it is scoped to GitHub API quota, not to agent outcomes.
And on a clean round, index.ts:983-986 resets both counters to zero.
Meanwhile issue selection in execute.ts:182-191 re-queries all open squad-labelled issues each round and applies only a label filter. There is no per-issue attempt count, no cooldown, no state carried between rounds about which items have already burned agent turns.
Impact
A single malformed or impossible issue silently consumes an agent turn every interval, forever. Over an overnight run at a 5 minute interval that is ~100 wasted turns on one bad item.
Because it is re-offered every round, it also crowds out genuinely actionable work in the same dispatch.
There is no signal to a human that a specific item is stuck - it looks identical to normal activity in the board report.
Proposal
Track attempts per work item, persisted alongside the existing circuit-breaker state in .squad/:
Record { itemId, attempts, lastAttemptAt, lastError } after each dispatch.
After N consecutive failed attempts on the same item (default 3, configurable), stop offering it to findExecutableIssues().
On the final strike, escalate visibly - comment on the issue, apply a squad:stuck label, and surface it in reportBoard().
Reset the counter when the item is edited or the label is removed, so a human fixing the issue puts it back in play.
This depends on having a real success signal, so it pairs naturally with adding a verification gate to the watch path.
Activity