List, inspect, and delete recorded agent runs from the terminal, with table or JSON output.

A trace is a recorded agent run — every LLM call, tool invocation, and error captured as spans. The traces commands let you browse and inspect them.

List traces

retrace traces list                              # Recent traces, newest first
retrace traces list --limit 50 --status completed
retrace traces list --project <project_id> --json

Use --json to pipe results into other tools:

retrace traces list --json | jq '.[].name'

Inspect a trace

retrace traces get <trace_id>            # Summary
retrace traces get <trace_id> --spans    # Include every span
retrace traces get <trace_id> --json     # Machine-readable output

For a full-screen, navigable view of a trace and its spans:

retrace traces get <trace_id> --interactive

Navigate with the arrow keys; press q to quit.

Delete traces

retrace traces delete <trace_id> --force

Bulk delete

Preview matching traces first, then delete with --force:

retrace traces bulk-delete --status failed          # Preview
retrace traces bulk-delete --status failed --force  # Delete
retrace traces bulk-delete --name "test-" --force   # Filter by name pattern

Output formats

Every list and get command accepts --json for scripting. The default is a readable table.

Next steps

Sessions — group related traces.
Forks — branch and replay a trace.
Streaming — tail spans in real time.

Traces