---
description: "Show every multi-agent task's ID, phase, branch, and status. Use when asked what is running, or for an overview of every task."
description-tr: "Tüm multi-agent görevlerinin ID, faz, branch ve durumunu gösterir."
---

# multi-agent status  -  Task Status Dashboard

Show every active and completed task as a table.

## Steps

1. **Detect the project**  -  find the repo root from cwd (otherwise scan every known repo):
   - `~/my-ios-app/.worktrees/`
   - `~/my-figma-app/.worktrees/`
   - `~/my-ui-components/.worktrees/`

2. **Scan worktrees**  -  read `agent-state.json` in each worktree dir. **Also scan the log dir**, because a task whose PR is open has no worktree any more (Phase 6 removes it and salvages its state): `find $HOME/.claude/logs/multi-agent -maxdepth 4 -name agent-state.json -path '*/artifacts/*'`. (`-maxdepth 4`, not 3: Phase 6 always passes `--project`, so the salvaged copy lands at `<project>/<task-id>/artifacts/agent-state.json`, which a depth-3 scan can never reach.) Merge both sets by `taskId`, preferring the worktree copy when both exist, and render a finalized task with its `worktreeRemovedAt` rather than omitting it  -  a task that shipped should not vanish from status.
   ```bash
   find {repo}/.worktrees/ -name "agent-state.json" -maxdepth 2
   ```

3. **Parse state**  -  for each task:
   - `taskId`, `branch`, `currentPhase`, `status`, `startedAt`, `autopilot`

4. **Render as a table**:
   ```
   🤖 Multi-Agent Tasks

   | ID | Jira/Task | Branch | Phase | Status | Duration |
   |----|-----------|--------|-------|--------|----------|
   | #1 | {JIRA-KEY}-12345 | feature/{JIRA-KEY}-12345-... | 7/7 DONE | ✅ Complete | 12m |
   | #3 | {JIRA-KEY}-12345 | feature/{JIRA-KEY}-12345-... | 7/7 DONE | ✅ Complete | 8m |

   💡 log #1 | resume #N | kill #N
   ```

6. **What is waiting to be learned** (one line, only when non-zero):

   ```bash
   node "$HOME/.claude/scripts/learn-from-transcripts.mjs" --json 2>/dev/null
   node "$HOME/.claude/scripts/observations.mjs" scan --status open --json 2>/dev/null
   ```

   Report `N lesson(s) minable from transcripts  -  /multi-agent:refactor to review` and `N open pipeline observation(s)` when either count is above zero, and print nothing when both are zero. Neither runs a model and neither writes anything: the miner is dry-run by default. Zero candidates alongside a non-zero `toolResultsExamined` means there is nothing to find; zero of both means the read is broken, and that is worth saying rather than reporting a clean queue.

5. **Quick command hints**  -  based on state:
   - Paused task → suggest `resume #N`
   - Done task → suggest `log #N`