# squadron mission

Execute a mission.

## Usage

```bash
squadron mission <mission-name> -c <config-path> [--input key=value...]
```

## Flags

| Flag | Description |
|------|-------------|
| `-c, --config` | Path to config directory (default: `.`) |
| `-d, --debug` | Enable debug mode (captures LLM messages) |
| `-i, --input` | Mission input as key=value (repeatable) |
| `--resume` | Resume a previously failed mission by its ID |

## Example

```bash
squadron mission data_pipeline -c ./my-config

squadron mission weather_report -c ./config --input city=Chicago
```

## Resume

If a mission fails or is interrupted, you can resume it using the mission ID displayed when it started:

```bash
squadron mission data_pipeline -c ./config --resume abc123def456
```

Resume rebuilds the exact state from stored sessions — completed tasks are skipped, and interrupted tasks pick up where they left off. Mission state is persisted to `.squadron/store.db`.

## Debug Mode

```bash
squadron mission -d -c ./config data_pipeline
```

Creates a `debug/` folder with:
- `events.log` - Task and tool events
- `commander_*.md` - Full commander conversations
- `agent_*.md` - Full agent conversations

## See Also

- [Missions Overview](/missions/overview)
- [Tasks](/missions/tasks)