Skip to main content

Run History CLI

Every recipe run is recorded automatically. Use recipe runs to see what happened, then feed a Run ID into recipe judge.

Quick Start

Commands

runs

List recipe run history.
Options: The table shows Recipe · Version · Status · When · Session · Run ID, with color-coded status (success green, failed red, policy_denied/timeout yellow). Examples:
Copy a Run ID from the table and pass it to praisonai recipe judge <run-id> to evaluate that execution.
If the history module can’t be imported, the command prints Run history unavailable: <error> and exits with code 1.

runs stats

Get storage statistics.
Output:

runs cleanup

Clean up old runs based on retention policy.

export

Export a run for replay or debugging.
Options: Examples:

replay

Replay a run from an export bundle.
Options: Examples:

Export Format

Automatic History Persistence

Every praisonai recipe run (and every run_stream() execution) is recorded to history automatically. You don’t need --save for a run to appear in recipe runs. History is independent of the recipe registry: runs for a deleted or unknown recipe are still listed. Disable persistence:
Re-enable (default):

Storage Location

Run history is stored at ~/.praison/runs/.

Data Policy

Runs respect the recipe’s data policy:

Python API

Next Steps