> ## Documentation Index
> Fetch the complete documentation index at: https://docs.breezeblue.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Breeze CLI history and jobs

> Retrieve past generations, track async jobs, and manage local playback and cache.

Every generation is recorded in your account history, and async generations run as jobs you can track. Both can be listed, downloaded, played, and scripted from the CLI.

## Generation history

```bash theme={null}
breeze history list
breeze history list --search "hello" --voice <voice_id> --page-size 20
breeze history get <history_item_id>
breeze history download <history_item_id> -o take.mp3
breeze history play <history_item_id>
```

Delete removes the item from your account. Scripts and agents must pass `--yes`:

```bash theme={null}
breeze history delete <history_item_id> --yes
```

## Async generation jobs

`breeze tts --async` returns a `generation_job_id` instead of audio. Track it with `breeze jobs`:

```bash theme={null}
breeze jobs get <generation_job_id>
breeze jobs wait <generation_job_id> --timeout 5m -o narration.mp3
breeze jobs download <generation_job_id> -o narration.mp3
breeze jobs play <generation_job_id>
```

`jobs wait` polls until the job completes (default timeout `2m`, poll interval `2s`). In JSON mode it writes one progress line per poll to `stderr` and the final job result to `stdout`, so machine callers can stream progress without losing the parseable result.

## Local playback and cache

`breeze play` plays any local or public WAV/MP3 file — including files another command just saved:

```bash theme={null}
breeze play hello.wav
breeze play https://example.com/clip.mp3
```

When you generate without `-o`, the CLI keeps audio in a local cache so a take is never lost:

```bash theme={null}
breeze cache dir
breeze cache list --type tts --limit 20
breeze cache get <id>
breeze cache clean --older-than 7d --yes
```

`cache list --type` accepts `all`, `tts`, `job`, `history`, `preview`, and `remote`. The cache lives in your system cache directory; override it with `--cache-dir` or `BREEZE_CACHE_DIR`.