Completed Tasks
Tasks in the Done column are archived automatically: the session is suspended with its context preserved, and the card leaves the board. The completed-tasks dialog, opened from the Done column, is where archived work lives - browse it, audit what each session cost, and bring tasks back when they need another round.
The Completed Tasks Table
Section titled “The Completed Tasks Table”Archived tasks render as a sortable table. Click any column header to sort by it:
| Column | What it shows |
|---|---|
| Title | The task title and display ID |
| Cost | Total API cost of the task’s sessions |
| Duration | How long the agent ran |
| Tokens | Total tokens consumed |
| Tools | Tool calls made across the task’s sessions |
| Files | Files changed |
| Lines | Lines added and removed |
| Completed | When the task was archived (the default sort, newest first) |
Clicking a row selects it; the actions on each row do the rest:
- The View details (eye) button opens the task’s session summary
- Restore to board opens a popover listing the board’s columns - pick one and the task returns there
When an archived task’s session is old enough that restoring it may no longer resume cleanly, the dialog warns you before you try.
Session Summary
Section titled “Session Summary”The session summary shows duration, model, cost, token usage, tool-call count, files changed, and lines added/removed. A collapsible By tool section breaks the calls down per tool (call count, total and average duration, and a Failed column when any call was interrupted); cost and token columns appear for agents that emit per-tool telemetry.
Bulk Operations
Section titled “Bulk Operations”Select multiple rows to act on them together:
- Restore - a popover picks the target column, and every selected task moves back to the board at once
- Delete - permanently remove the selected tasks along with their sessions and worktrees
Resuming Archived Work
Section titled “Resuming Archived Work”Restoring a task to an active column resumes its suspended session with full context intact - the agent picks up the conversation where it left off. Moving a task to Done frees its worktree’s disk space but keeps everything needed to resume; dragging it back to an active column recreates the worktree (see Worktree Lifecycle).
The move out of Done is the route back, and the only one. Since v0.36.0, pressing Resume on a task still sitting in Done is refused with “This task is complete. Move it out of Done to continue working on it.” Resuming in place would rebuild the worktree and put a live agent on a task with no board card, burning quota with nothing on screen to notice it. Moving the task out unarchives it first and then spawns through the normal path. See When resume is refused.
The unarchive happens the moment you move the card, not when the spawn lands, and the card reports the restore as in progress rather than as Paused - so a slow worktree rebuild reads as work happening rather than as a stall.
Finding Archived Tasks
Section titled “Finding Archived Tasks”Quick Find searches archived tasks too - hits that are archived carry a small archived badge so you can tell finished work from live cards in the results.
Next steps
Section titled “Next steps”Next: Backlog - the other end of the pipeline, where tasks wait before reaching the board.
See also:
- Creating Tasks - authoring tasks and the task lifecycle
- Session Persistence - how suspended sessions survive restarts
- Git Worktrees - what happens to a task’s worktree at each move
Kangentic is free and open source. A star helps other people find it.
Star on GitHub