Run History CLI
Every recipe run is recorded automatically. Userecipe runs to see what happened, then feed a Run ID into recipe judge.
Quick Start
Commands
runs
List recipe run history.
The table shows Recipe · Version · Status · When · Session · Run ID, with color-coded status (
success green, failed red, policy_denied/timeout yellow).
Examples:
Run history unavailable: <error> and exits with code 1.
runs stats
Get storage statistics.runs cleanup
Clean up old runs based on retention policy.export
Export a run for replay or debugging.
Examples:
replay
Replay a run from an export bundle.
Examples:
Export Format
Automatic History Persistence
Everypraisonai 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:
Storage Location
Run history is stored at~/.praison/runs/.
Data Policy
Runs respect the recipe’s data policy:Python API
Next Steps
- Recipe Registry - Publish and pull recipes
- Security Features - SBOM, signing, auditing
- Policy Packs - Manage tool permissions

