cleveragents/cleveragents-core

Fork 3

UAT: CLI `-v` verbosity flag does not control log level — verbose mode not wired to structlog #5830

New issue

Open

opened 2026-04-09 10:19:33 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 10:19:33 +00:00

Owner

Bug Report

Feature Area: Debug Logging — Verbose Mode
Milestone: v3.5.0 (M6)
Severity: Priority/Backlog — usability gap, not blocking

What Was Tested

The CLI verbosity flag (-v) was inspected against the specification's debug logging requirements.

Expected Behavior (from spec)

The specification states:

The CLI supports increasing verbosity for debugging via the -v flag (up to 5 levels, from ERROR to TRACE).
Log output is sent to stderr by default to keep it separate from command output on stdout.

The spec defines 5 verbosity levels:

(no flag) = ERROR
-v = WARNING
-vv = INFO
-vvv = DEBUG
-vvvv = TRACE

Actual Behavior

The main CLI callback (src/cleveragents/cli/main.py) hardcodes log_level="WARNING" for all commands:

@app.callback()
def main_callback(...):
    configure_structlog(log_level="WARNING")

The -v flag is only implemented for agents actor run and agents actor commands (in src/cleveragents/cli/commands/actor.py and actor_run.py), but is not a global CLI option on the root app callback.

The configure_structlog() function supports log_level parameter, but the global CLI never passes the verbosity count to it. The build shortcut command has a --verbose/-v flag but it only controls output detail, not log level.

There is no global -v/--verbose count option on the root agents command that maps to structlog levels.

Code Location

src/cleveragents/cli/main.py — main_callback() hardcodes WARNING level
src/cleveragents/config/logging.py — configure_structlog() supports levels but is not called with user-provided level
src/cleveragents/cli/commands/actor.py — only actor subcommand has -v count

Steps to Reproduce

Run agents -vvv plan list — no additional debug output appears
Run agents --help — no -v global flag is listed

Impact

Developers cannot enable debug logging for troubleshooting without modifying environment variables. The spec's promised 5-level verbosity system is not accessible via the CLI.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area**: Debug Logging — Verbose Mode **Milestone**: v3.5.0 (M6) **Severity**: Priority/Backlog — usability gap, not blocking ### What Was Tested The CLI verbosity flag (`-v`) was inspected against the specification's debug logging requirements. ### Expected Behavior (from spec) The specification states: > The CLI supports increasing verbosity for debugging via the `-v` flag (up to 5 levels, from ERROR to TRACE). > Log output is sent to `stderr` by default to keep it separate from command output on `stdout`. The spec defines 5 verbosity levels: - (no flag) = ERROR - `-v` = WARNING - `-vv` = INFO - `-vvv` = DEBUG - `-vvvv` = TRACE ### Actual Behavior The main CLI callback (`src/cleveragents/cli/main.py`) hardcodes `log_level="WARNING"` for all commands: ```python @app.callback() def main_callback(...): configure_structlog(log_level="WARNING") ``` The `-v` flag is only implemented for `agents actor run` and `agents actor` commands (in `src/cleveragents/cli/commands/actor.py` and `actor_run.py`), but is **not** a global CLI option on the root `app` callback. The `configure_structlog()` function supports `log_level` parameter, but the global CLI never passes the verbosity count to it. The `build` shortcut command has a `--verbose/-v` flag but it only controls output detail, not log level. There is no global `-v`/`--verbose` count option on the root `agents` command that maps to structlog levels. ### Code Location - `src/cleveragents/cli/main.py` — `main_callback()` hardcodes `WARNING` level - `src/cleveragents/config/logging.py` — `configure_structlog()` supports levels but is not called with user-provided level - `src/cleveragents/cli/commands/actor.py` — only `actor` subcommand has `-v` count ### Steps to Reproduce 1. Run `agents -vvv plan list` — no additional debug output appears 2. Run `agents --help` — no `-v` global flag is listed ### Impact Developers cannot enable debug logging for troubleshooting without modifying environment variables. The spec's promised 5-level verbosity system is not accessible via the CLI. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 referenced this issue

2026-04-09 10:25:17 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 13) #5754

HAL9000 added the

labels

2026-04-09 10:55:32 +00:00

~~HAL9000 referenced this issue 2026-04-09 10:56:39 +00:00~~

[AUTO-UAT-POOL] UAT Testing Report (Cycle 1) #5750

HAL9000 added

and removed

labels

2026-04-09 11:14:00 +00:00

HAL9000 referenced this issue

2026-04-09 11:21:43 +00:00

[AUTO-ARCH] Architecture Review (Cycle 1) #5767

HAL9000 referenced this issue

2026-04-09 11:21:49 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 29) #5788

HAL9000 added this to the v3.5.0 milestone

2026-04-09 14:08:47 +00:00

HAL9000 commented

2026-04-09 14:13:41 +00:00

Author

Owner

Milestone compliance fix applied:

Assigned to milestone: v3.5.0 (Autonomy Hardening)
Reason: Issue is State/Verified but had no milestone. Issue body explicitly states "Milestone: v3.5.0 (M6)" — CLI verbosity flag belongs to v3.5.0 scope.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Milestone compliance fix applied: - Assigned to milestone: **v3.5.0** (Autonomy Hardening) - Reason: Issue is `State/Verified` but had no milestone. Issue body explicitly states "Milestone: v3.5.0 (M6)" — CLI verbosity flag belongs to v3.5.0 scope. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 referenced this issue

2026-04-09 14:26:04 +00:00

[AUTO-GROOMER] Backlog Grooming Report (Cycle 1) #6079