dispatch status: list active-or-recent dispatches, not just the newest #30

Closed
opened 2026-05-28 04:56:58 +00:00 by coilysiren · 0 comments
Owner

coily dispatch status with no arguments shows only the single most recent dispatch. That is not enough when several dispatches are in flight - especially now that cascade fans out many concurrent workers.

Change

Make bare dispatch status list every dispatch that is still running OR was spawned within a time window (--since, default 1h), newest first, one compact line each (ref, pid + RUNNING/EXITED, spawn-relative, log path). Running dispatches always show regardless of age, so a long-running worker never falls off the list. --all lists everything on disk.

Targeting a single dispatch by <owner/repo#N> or --pid still renders the full block (pid line, spawn time, log tail). --follow is unchanged (single-target, or newest when bare).

This unifies the two natural asks - "show me what's active" and "show me what ran recently" - into one window: active-or-recent.

`coily dispatch status` with no arguments shows only the single most recent dispatch. That is not enough when several dispatches are in flight - especially now that `cascade` fans out many concurrent workers. ## Change Make bare `dispatch status` list every dispatch that is still running OR was spawned within a time window (`--since`, default 1h), newest first, one compact line each (ref, pid + RUNNING/EXITED, spawn-relative, log path). Running dispatches always show regardless of age, so a long-running worker never falls off the list. `--all` lists everything on disk. Targeting a single dispatch by `<owner/repo#N>` or `--pid` still renders the full block (pid line, spawn time, log tail). `--follow` is unchanged (single-target, or newest when bare). This unifies the two natural asks - "show me what's active" and "show me what ran recently" - into one window: active-or-recent.
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/cli-guard#30
No description provided.