Different feature from the Run-State Journal. This page is about context replay — recording a run’s trace and stepping through it in a debugger. The run-state journal is about resumable execution — persisting the per-event cursor so a crashed run continues without re-executing tools. Pick the run-state journal for crash-safe production runs; pick context replay to inspect a completed run for debugging.
Quick Start
1
Simple Usage
Save a trace during a recipe or workflow run:
2
With Configuration
Emit traces from Python and persist to disk:
How It Works
Traces are stored as JSONL in
~/.praisonai/traces/.
CLI Commands
Interactive navigation
Inreplay context: Enter/n next, p previous, g <N> go to event, q quit.
Filters
Common Patterns
In-memory trace during tests
Read traces programmatically
Cleanup old traces
Best Practices
Use meaningful session IDs
Use meaningful session IDs
Include a timestamp or task identifier so traces are easy to find in
replay list.Keep redaction enabled
Keep redaction enabled
redact=True (default) strips sensitive data from persisted traces.Use snapshots sparingly
Use snapshots sparingly
Full
CONTEXT_SNAPSHOT events can be large — prefer message and tool events for routine debugging.Run cleanup periodically
Run cleanup periodically
Use
replay cleanup --max-age 7 so trace storage does not grow unbounded on developer machines.Related
Run History
Inspect past agent runs and session metadata
Observability Hooks
Emit structured events for external observability tools

