Two actions take a task off your list, and they apply to tasks in different states: Delete removes a pending task you never ran, and Archive hides a cancelled task while keeping its record. Both are different from cancelling a run, which stops work in progress — see Cancel a running task for that.
Each task carries whichever action fits its state, on its row in the task list and on its detail page.
Delete a pending task
Delete is available only on a Pending task — one that has never run, so there’s no run history or cost to keep. It’s the red Delete action; selecting it opens a Delete Task confirmation before anything happens.
Whether a deleted task can come back depends on where it came from:
- From a labelled issue (GitHub or Jira) — deleting removes the task, but if the source issue still carries the
dijjilabel, re-applying the label re-creates it. See Where tasks come from. - From a request breakdown — the task can’t be recovered. There’s no issue label behind it to re-create it, so deletion is final.
The confirmation dialog spells out which case applies before you confirm.
Archive a cancelled task
Archive is available only on a Cancelled task. Unlike delete, it takes effect immediately — there’s no confirmation step — and it doesn’t destroy anything: it hides the task from the list but keeps its run history and cost.
An archived task isn’t gone. It moves out of the default view and shows up under the Archived filter in the List view — see Switch task views. Use archive to clear finished-with, cancelled tasks out of the way without losing the record of what they cost.
What each state allows
| Task state | Available action |
|---|---|
| Pending | Delete (permanent, with confirmation) |
| Queued or Running | Cancel the run — see Cancel a running task |
| Cancelled | Archive (immediate, hides but keeps history) |
| Completed or Failed | Stays on the list; a failed task can be re-run |