Summary
After upgrading to a newer version of looper, the default looper ps output became noisy because old manual_intervention fixer loops are shown alongside currently running work. These entries are mostly historical PR tasks whose PRs are already closed or merged, but they still dominate the process list.
Example
Sanitized example output:
$ looper ps
# type target step agent pid status age
--- -------- --------------------- ------ ----- --- ------------------- ------
375 reviewer org-a/repo-a#3151 review - - running 3m
376 fixer org-b/repo-b#137 repair - - running 3m
234 fixer org-a/repo-a#2573 - - - manual_intervention 1d23h
262 fixer org-a/repo-a#2716 - - - manual_intervention 3d16h
39 fixer org-c/repo-c#5 - - - manual_intervention 16d21h
38 fixer org-c/repo-d#41 - - - manual_intervention 16d22h
36 fixer org-c/repo-e#86 - - - manual_intervention 17d15h
35 fixer org-c/repo-c#1 - - - manual_intervention 17d19h
1 fixer org-a/repo-f#10 - - - manual_intervention 30d17h
Several of the stale fixer targets in this list correspond to PRs that are already closed or merged.
Actual behavior
looper ps shows old manual_intervention fixer loops by default, even when they are not active and have no agent/pid. This makes it hard to see the two currently running tasks.
looper run reconcile-stale followed by looper queue cleanup --stale does not remove these entries from looper ps.
Expected behavior
The default looper ps view should stay focused on active/actionable work. Historical manual_intervention loops should either:
- be hidden from the default view and remain visible via
looper ps --status manual_intervention or looper ps --all, or
- have a supported cleanup/acknowledge command that removes closed/merged PR tasks from the default process list.
Why this matters
After upgrade, the process list appears dirty and makes it harder to notice real running work. The user has to mentally filter out stale manual-intervention items every time.
Notes
There does not appear to be a dedicated CLI command to clear a single manual_intervention loop/queue item. queue cleanup --stale only handles stale queued items, not these paused/failed manual-intervention records.
Summary
After upgrading to a newer version of looper, the default
looper psoutput became noisy because oldmanual_interventionfixer loops are shown alongside currently running work. These entries are mostly historical PR tasks whose PRs are already closed or merged, but they still dominate the process list.Example
Sanitized example output:
Several of the stale fixer targets in this list correspond to PRs that are already closed or merged.
Actual behavior
looper psshows oldmanual_interventionfixer loops by default, even when they are not active and have no agent/pid. This makes it hard to see the two currently running tasks.looper run reconcile-stalefollowed bylooper queue cleanup --staledoes not remove these entries fromlooper ps.Expected behavior
The default
looper psview should stay focused on active/actionable work. Historicalmanual_interventionloops should either:looper ps --status manual_interventionorlooper ps --all, orWhy this matters
After upgrade, the process list appears dirty and makes it harder to notice real running work. The user has to mentally filter out stale manual-intervention items every time.
Notes
There does not appear to be a dedicated CLI command to clear a single
manual_interventionloop/queue item.queue cleanup --staleonly handles stale queued items, not these paused/failed manual-intervention records.