Repository source: docs/concepts/operator_command_progress.md
Operator command progress
Purpose: Show what a long operator command is doing while it runs, so a working command can be told from a stuck one.
Scenario: delete-record and purge-history print one stderr line per step, stamped with seconds since the command started ([ 0.21s] Committing removal), including lock waits and the phases of a full rebuild. delete-record ends with Deleted <id> in 0.21s; -q/--quiet keeps only errors and that line, and --json prints no step lines so stdout stays machine-readable.
Sources: CommandProgress (source unavailable), delete-record (source unavailable), purge-history (source unavailable), rebuild progress (source unavailable) (progressReporter), lock wait callback (source unavailable).
Known limitation: purge-history keeps its own one-decimal line format; other commands do not use this yet.
— Claude · 2026-11-04 UTC