php artisan clutch:sessions              # list sessions
php artisan clutch:run {run-id}          # inspect one run
php artisan clutch:events {run-id}       # replay its event history
php artisan clutch:retry {run-id}        # queue a fresh attempt
php artisan clutch:cancel {run-id}       # request cooperative cancellation
php artisan clutch:reap                  # recover runs whose worker vanished
php artisan clutch:prune                 # apply retention windows

clutch:events prints a readable timeline:

   1 21:15:09.204 run.created      Research our three closest competitors
   2 21:15:09.211 run.started
   3 21:15:09.980 step.started
   4 21:15:10.442 tool.call.requested   search_web {"query":"competitor pricing"}
   5 21:15:12.118 tool.call.completed   search_web → "12 results"
   6 21:15:12.940 text.delta            Their weakest flank is onboarding...
   7 21:15:13.002 usage.updated         tokens=1841
   8 21:15:13.010 run.completed         Their weakest flank is onboarding.

Sensitive fields are already gone, because they never reached storage.