tt mission

Autonomous multi-issue mission mode commands.

Synopsis

tt mission start [OPTIONS]
tt mission status [OPTIONS]
tt mission resume <RUN_ID>
tt mission dispatch [--run <RUN_ID>] [--once]
tt mission note <RUN_ID> <MESSAGE>
tt mission stop <RUN_ID> [OPTIONS]
tt mission list [OPTIONS]

Description

Mission mode enables durable, dependency-aware orchestration of multiple GitHub issues with automatic PR/CI monitoring. Use these commands to start, monitor, and control missions.

tt mission start bootstraps the mission graph and performs an initial scheduling pass. tt mission dispatch is the persistent runtime loop that keeps the mission moving, monitors watches, and assigns follow-up work.

Subcommands

tt mission start

Start a new mission with one or more objectives.

tt mission start --issue <ISSUE>... [--doc <PATH>...] [OPTIONS]

Options:

Issue Formats:

• 23 — Issue #23 in current repo
• owner/repo#23 — Fully qualified issue
• https://github.com/owner/repo/issues/23 — Full URL

Examples:

# Start with single issue
tt mission start --issue 23

# Multiple issues
tt mission start -i 23 -i 24 -i 25

# Cross-repo issues
tt mission start --issue my-org/other-repo#42

# Include a design doc
tt mission start --issue 23 --doc docs/design.md

# Allow more parallelism
tt mission start -i 23 -i 24 --max-parallel 4

# Skip reviewer gate
tt mission start -i 23 --no-reviewer

tt mission status

Show status of missions.

tt mission status [--run <ID>] [--work] [--watch] [--dispatcher]

Options:

Examples:

# Show all active missions
tt mission status

# Specific mission with work items
tt mission status --run abc123 --work

# Include watch items
tt mission status -r abc123 --work --watch

# Include dispatcher/operator-control details
tt mission status -r abc123 --dispatcher

Output:

🎯 Mission Status
   ID: abc123-def456-...
   State: 🚀 Running
   Created: 2024-01-15 10:30:00 UTC
   Updated: 2024-01-15 11:45:00 UTC

📋 Objectives: 3
   - redis-field-engineering/tinytown#23
   - redis-field-engineering/tinytown#24
   - redis-field-engineering/tinytown#25

⚙️  Policy:
   Max parallel: 2
   Reviewer required: true
   Auto-merge: false
   Watch interval: 180s

⏰ Next Wake: 2024-01-15 11:48:00 UTC

📦 Work Items: 5
   🔵 ready    Issue #23: Implement auth flow
   🔄 running  Issue #24: Add rate limiting (→ backend)
   ⏳ pending  Issue #25: Write tests

tt mission resume

Resume a stopped or blocked mission.

tt mission resume <RUN_ID>

Examples:

tt mission resume abc123-def456-...

tt mission dispatch

Run the persistent dispatcher loop that owns mission progression.

tt mission dispatch [--run <RUN_ID>] [--once]

Options:

Examples:

# Run dispatcher for all active missions
tt mission dispatch

# Single mission only
tt mission dispatch --run abc123-def456-...

# One-shot tick for debugging/tests
tt mission dispatch --run abc123-def456-... --once

tt mission note

Queue a conductor/operator note for the dispatcher to consume on its next tick.

tt mission note <RUN_ID> <MESSAGE>

Examples:

# Ask the dispatcher to retry now
tt mission note abc123-def456-... "resume and retry now"

# Pause a mission with operator context
tt mission note abc123-def456-... "pause until product decision is made"

tt mission stop

Stop an active mission.

tt mission stop <RUN_ID> [--force]

Options:

Examples:

# Graceful stop (can be resumed)
tt mission stop abc123

# Force stop (cannot be resumed)
tt mission stop abc123 --force

tt mission list

List all missions.

tt mission list [--all]

Options:

Examples:

# Active missions only
tt mission list

# All missions including completed
tt mission list --all

Work Item States

See Also

• Mission Mode Concept
• Mission Mode Tutorial
• tt status
• tt conductor