Skip to content

UI and Output

Leonard Ramminger edited this page Aug 9, 2026 · 1 revision

UI and Output

Beez prints progress, summaries, and optional logs while a pipeline runs. Most behavior is controlled under the ui section in config. CLI flags can override output mode and log file paths for a single run.

Contents

Minimal config

ui = {
    output_mode = "clean",
    colors = true,
    theme = "gruvbox",
    summary = "simple",
    logging = {
        run_log = true,
        run_log_file = ".cache/logs/latest.log",
        workers = "on_failure",
        workers_dir = ".cache/logs/workers",
    },
}

What appears where

Output clean verbose errors silent
Progress lines yes yes no no
Successful command output no yes no no
Failure output yes yes yes no
Run summary on success yes yes no no
Run summary on failure yes yes yes no
CLI error messages yes yes yes no

Run logs on disk are independent of output mode unless you disable them in config or with --no-log-file.

CLI overrides

beez --verbose build      # verbose output mode
beez --error build        # errors mode
beez --silent build       # silent mode
beez --log-file /tmp/beez.log build
beez --no-log-file build

See Output and Logging Flags for the full CLI list.

Practical combinations

Quiet local runs:

ui = {
    output_mode = "clean",
    hide_cache_hits = true,
    summary = "minimal",
}

CI with artifacts:

ui = {
    output_mode = "verbose",
    logging = {
        run_log = true,
        run_log_file = "report/beez.log",
        workers = "always",
    },
}

Debugging a failing step:

beez --verbose -j 1 -s my-step

Then inspect .cache/logs/workers/ if worker logs are enabled.

Related pages

Clone this wiki locally