status

Task Harness Status

Displays the current status and progress of task harness sessions.

Overview

The status skill provides visibility into task harness sessions by:

• Listing all sessions (active, completed, failed, cancelled)
• Showing detailed progress for specific sessions
• Displaying task-by-task status with visual indicators
• Reporting retry counts, iteration numbers, and validation results

Prerequisites

• Session files - At least one session in .claude/task-harness/sessions/

Instructions

Step 1: Find Sessions

List all session files in .claude/task-harness/sessions/:

ls -la .claude/task-harness/sessions/*.json 2>/dev/null

Step 2: Parse Session Data

For each session (or specific session if ID provided), extract:

SESSION_ID=$(jq -r '.sessionId' "$STATE_FILE")
HARNESS_NAME=$(jq -r '.harnessName' "$STATE_FILE")
STATUS=$(jq -r '.status' "$STATE_FILE")
CURRENT_INDEX=$(jq -r '.currentTaskIndex' "$STATE_FILE")
TOTAL_TASKS=$(jq -r '.totalTasks' "$STATE_FILE")

Step 3: Build Task Summary

For each task, determine status indicator:

• ✓ - Complete
• → - In Progress
• ○ - Pending
• ✗ - Failed
• ⊘ - Blocked

Step 4: Format Output

Display comprehensive status information with visual task list.

Output

Single Session Output

Task Harness Status
===================
Session: 1234567890-12345
Harness: implement-auth-feature
Status: running
Progress: 2/5 tasks (40%)
Current: Task 3 - Implement Auth Routes

Task Summary:
  ✓ 1. Design Authentication System [complete]
  ✓ 2. Implement User Model [complete]
  → 3. Implement Auth Routes [in_progress] (iteration 12, retry 0)
  ○ 4. Write Tests [pending]
  ○ 5. Update Documentation [pending]

Last Activity: 2024-01-15 12:34:56

Multiple Sessions Output

Task Harness Sessions
=====================

Session 1:
  ID: 1234567890-12345
  Harness: implement-auth-feature
  Status: running
  Progress: 2/5 tasks

Session 2:
  ID: 1234567891-54321
  Harness: fix-critical-bugs
  Status: completed
  Progress: 3/3 tasks

Use /task-harness:status <session-id> for details

No Sessions Output

No task harness sessions found.

To start a new session:
  /task-harness:start <yaml-file>

Or create a task file interactively:
  /task-harness:create

Error Handling

Error	Cause	Resolution
No sessions found	Empty sessions directory	Start a new session with /task-harness:start
Session not found	Invalid session ID	Check available sessions without ID argument
Corrupted state	Malformed JSON	Check logs, consider archiving and restarting

Examples

Example 1: Check All Sessions

User: /task-harness:status

Skill: Lists all sessions with summary

Result:
Task Harness Sessions
=====================
1. 1234567890-12345 (auth-feature) - running - 2/5 tasks
2. 1234567891-54321 (bug-fixes) - completed - 3/3 tasks

Example 2: Check Specific Session

User: /task-harness:status 1234567890-12345

Skill: Shows detailed status for that session

Result:
Task Harness Status
===================
Session: 1234567890-12345
Harness: implement-auth-feature
Status: running
Progress: 2/5 tasks (40%)

Task Summary:
  ✓ 1. Design Authentication System [complete]
  → 2. Implement User Model [in_progress]
  ○ 3. Implement Auth Routes [pending]
  ...

Example 3: Check Failed Session

User: /task-harness:status 1234567890-12345

Skill: Shows failed session with error details

Result:
Task Harness Status
===================
Session: 1234567890-12345
Status: failed
Failed at: Task 4 - Write Tests
Reason: Max retries exceeded (2/2)

Last Validation Error:
  Type: tests_must_pass
  Message: Tests failed (exit code 1): 3 tests failed
  Timestamp: 2024-01-15T12:00:00Z

To retry: /task-harness:resume 1234567890-12345

Resources

• {baseDir}/docs/yaml-schema.md - Session state structure documentation
• {baseDir}/scripts/cleanup-harness.sh - Archive old sessions