-
Notifications
You must be signed in to change notification settings - Fork 0
UI and Output
Leonard Ramminger edited this page Aug 9, 2026
·
1 revision
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.
-
Output Modes -
clean,verbose,errors, andsilent - Progress and Animation - progress lines, bars, spinners, cache hits
- Colors and Themes - palettes, truecolor, icons
- Run Summaries - end-of-run message styles
- Logging and Log Files - run logs, step logs, worker capture
-
Config Reference - full
ui.*key list
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",
},
}| 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.
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 buildSee Output and Logging Flags for the full CLI list.
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-stepThen inspect .cache/logs/workers/ if worker logs are enabled.
- Configuration Overview - how config layers merge
- Output and Logging Flags - CLI flags for this chapter
- Caching - cache hits in progress and summaries
-
Project Layout -
.cache/logs/location
Quick Reference · Glossary · FAQ
- Fundamentals
- Core Concepts
- Project Layout
- First Pipeline
- Phases and Scopes
- How Phases and Scopes Work
- Selecting with Phases and Scopes
- Designing Phases and Scopes
- Parallel Execution and Dependencies
- Configuration
- Configuration Overview
- Global User Config
- Project Config
- Environment Variables
- Performance Settings
- Cache Settings
- Config Reference
- CLI
- CLI Overview
- Running Targets
- Filtering by Phase
- Running a Single Step
- Listing Entities
- Output and Logging Flags
- Cache and Maintenance Flags
- Meta and Utility Commands
-
Project Scaffolding —
beez --init(embedded Tempify) - CLI Flag Reference
- Lua DSL
- DSL Overview
- Plugin System — Plugins, Config DSL, Standard-Workflows
- Step Declaration
- Task Declaration
- Workflow Declaration
- Order Declaration
- Configure Step
- ReqPack Declaration
- Beez API
- Step Context
- DSL Patterns
- Caching
- Caching Overview
- Step Cache
- Success Cache
- Glob Metadata Cache
- Artifact Patterns
- Cache Keys and Invalidation
- Cache Storage and Maintenance
- Caching Troubleshooting
- UI and Output
- Output Modes
- Progress and Animation
- Colors and Themes
- Run Summaries
- Logging and Log Files
- Development and Contribution
- Building and Setup
- Repository Layout
- Testing
- Code Quality
- Feature Development Workflow
- Submitting Changes