Quick Start
How It Works
| Event type | Description |
|---|---|
SESSION_START / SESSION_END | Session boundaries |
AGENT_START / AGENT_END | Agent lifecycle |
AGENT_HANDOFF | Handoff to another agent |
MESSAGE_ADDED | Context message appended |
TOOL_CALL_START / TOOL_CALL_END | Tool execution |
LLM_REQUEST / LLM_RESPONSE | LLM API calls |
CONTEXT_SNAPSHOT | Full context state captured |
~/.praisonai/traces/.
CLI Commands
| Command | Purpose |
|---|---|
praisonai replay list | List available traces |
praisonai replay context <id> | Interactive step-through |
praisonai replay flow <id> | Agent flow visualisation |
praisonai replay show <id> | Dump events (non-interactive) |
praisonai replay delete <id> | Delete a trace |
praisonai replay cleanup | Remove old traces |
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

