Wire the --verbose flag to the logger #7

New issue

Closed

opened 2026-08-17 19:31:18 +00:00 by rosa · 0 comments

rosa commented

2026-08-17 19:31:18 +00:00

Owner

What to build

tomate -v should print the log lines the code already emits. Right now the --verbose flag is parsed and then thrown away: Args carries a clap_verbosity_flag::Verbosity field that nothing ever reads, and the logger is initialised with no filter derived from it. Every info! in the codebase — creating the config file, writing the state file, archiving to history, executing a hook — is invisible unless the user happens to set RUST_LOG.

$ tomate -v pom stop
(no output at all)

The flag's verbosity level should drive the logger's filter, so -v, -vv and -q behave the way the flag's own help text implies.

Acceptance criteria

tomate -v <command> prints the info! lines that command emits, without RUST_LOG set
Increasing verbosity (-vv, -vvv) admits progressively more detail, and -q suppresses output
An explicit RUST_LOG still works, or the interaction between the two is documented in the flag's help
No log output appears at the default verbosity for a normal successful command

Blocked by

None — can start immediately.

## What to build `tomate -v` should print the log lines the code already emits. Right now the `--verbose` flag is parsed and then thrown away: `Args` carries a `clap_verbosity_flag::Verbosity` field that nothing ever reads, and the logger is initialised with no filter derived from it. Every `info!` in the codebase — creating the config file, writing the state file, archiving to history, executing a hook — is invisible unless the user happens to set `RUST_LOG`. ``` $ tomate -v pom stop (no output at all) ``` The flag's verbosity level should drive the logger's filter, so `-v`, `-vv` and `-q` behave the way the flag's own help text implies. ## Acceptance criteria - [ ] `tomate -v <command>` prints the `info!` lines that command emits, without `RUST_LOG` set - [ ] Increasing verbosity (`-vv`, `-vvv`) admits progressively more detail, and `-q` suppresses output - [ ] An explicit `RUST_LOG` still works, or the interaction between the two is documented in the flag's help - [ ] No log output appears at the default verbosity for a normal successful command ## Blocked by None — can start immediately.

rosa referenced this issue

2026-08-17 19:32:00 +00:00

Surface timer-scheduling failures instead of hiding or panicking #11

rosa added the

workflow

ready-for-agent

label

2026-08-17 19:32:07 +00:00

rosa referenced this issue from a commit

2026-08-17 22:00:18 +00:00

fix: Wire the verbosity flags to the logger

rosa closed this issue