Problem
When dolt.auto-commit: on is configured, every bd write operation (bd update, bd label add, bd close, etc.) prints a multi-line auto-push warning/status message to stderr. In a typical workflow with 5+ status updates, this generates ~90 seconds of noise that agents may misinterpret as errors.
Example
bd update lista-123 --status in_progress
✓ Updated issue: lista-123
dolt auto-push: throttled (last push 2m ago, interval 5m0s)
backup: throttled (last backup 3m ago, interval 15m0s)
Repeated for every single write.
Proposed Fix
Option A: Suppress throttle messages when using --quiet flag
Option B: Only show push messages when a push actually occurs (not when throttled)
Option C: Add config dolt.auto-push-quiet: true to suppress status lines
Context
Bead: lista-gnf. Five status updates = 5 warning walls = ~90s of noise in agent output.
Problem
When
dolt.auto-commit: onis configured, everybdwrite operation (bd update,bd label add,bd close, etc.) prints a multi-line auto-push warning/status message to stderr. In a typical workflow with 5+ status updates, this generates ~90 seconds of noise that agents may misinterpret as errors.Example
Repeated for every single write.
Proposed Fix
Option A: Suppress throttle messages when using
--quietflagOption B: Only show push messages when a push actually occurs (not when throttled)
Option C: Add config
dolt.auto-push-quiet: trueto suppress status linesContext
Bead:
lista-gnf. Five status updates = 5 warning walls = ~90s of noise in agent output.