Skip to content

fix(progress): quiet non-tty verbose success output#647

Merged
mstykow merged 2 commits intomainfrom
fix/verbose-nontty-progress
Apr 13, 2026
Merged

fix(progress): quiet non-tty verbose success output#647
mstykow merged 2 commits intomainfrom
fix/verbose-nontty-progress

Conversation

@mstykow
Copy link
Copy Markdown
Owner

@mstykow mstykow commented Apr 13, 2026

Summary

  • stop non-TTY --verbose runs from printing one success line per scanned file
  • keep bounded scan lifecycle messages in CI while preserving per-file warning and error detail
  • update the architecture and rollout docs to describe the new TTY-aware verbose behavior

Scope and exclusions

  • Included: progress UX changes in src/progress.rs, regression coverage in tests/progress_cli_integration.rs, and doc updates for the current verbose-mode contract
  • Explicit exclusions: no CLI flag changes, no output schema changes, and no compatibility shim for the unreleased CLI surface

mstykow and others added 2 commits April 13, 2026 23:20
Keep verbose path-by-path progress for interactive terminals, but avoid flooding CI logs with one success line per scanned file. Non-TTY verbose runs now emit bounded scan lifecycle messages while still preserving per-file warning and error context.

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Document that verbose mode keeps per-file success paths for interactive terminals while degrading to bounded scan lifecycle output plus per-file warning and error context when stderr is redirected. This keeps the architecture and rollout docs aligned with the current CI-facing UX.

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
@mstykow mstykow enabled auto-merge (rebase) April 13, 2026 21:31
@mstykow mstykow merged commit 0d00ef7 into main Apr 13, 2026
14 checks passed
@mstykow mstykow deleted the fix/verbose-nontty-progress branch April 13, 2026 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant