mission

Harness Mission — Autonomous Workflow Control

Create, monitor, and manage autonomous missions from Claude Code. Missions are multi-task workflows executed by The Harness orchestrator — each task spawns an independent Claude CLI session.

Prerequisites

Call harness_status to verify the daemon is running.

Commands

Create a Mission

1. Ask the user for: title, description, and which repos to target
2. Call harness_create_mission with the details
3. Report the mission ID and link to dashboard

Note: Missions need tasks before they can start. Tasks are typically added via the dashboard's decomposition feature or REST API.

Monitor a Mission

1. Call harness_get_mission to get the overview
2. Call harness_get_mission_tasks to see all tasks with statuses
3. Present a text-based progress view:

Mission: {title} [{status}]
Tasks: {completed}/{total} ({running} running, {review} in review)

  [completed] Task 1: Set up database schema
  [running]   Task 2: Implement API endpoints
  [review]    Task 3: Write integration tests  ← needs approval
  [pending]   Task 4: Deploy to staging

Handle Review Gates

When tasks reach review status, they need human approval:

1. Call harness_get_mission_tasks to find tasks in review state

2. For each review task, present the task details and ask the user

3. Based on user decision:

   • Approve: Call harness_approve_task — task moves to completed, downstream tasks unblock

   • Reject: Call harness_reject_task with feedback — task resets to pending with incremented retry count, feedback appended to description

Start / Pause

• Start: Call harness_start_mission — sets status to running, orchestrator begins dispatching tasks

• Pause: Call harness_pause_mission — stops new task dispatch, running tasks continue to completion

List Missions

Call harness_list_missions with optional status filter to see recent missions.

Interaction Style

• Keep status updates concise — use the text progress view, not verbose descriptions

• For review gates, show the task title and any output/artifacts before asking for approval

• Don't ask for confirmation on read-only operations (list, get, status)

• Do ask for confirmation before start, pause, approve, reject