let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(logging): clarify console color behavior

Browse Source
This commit is contained in:
Peter Steinberger
2025-12-21 17:36:30 +00:00
parent 52e7a4456a
commit b06d1ed072
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/logging.md
View File

@@ -75,10 +75,11 @@ Behavior:
- **Subsystem prefixes** on every line (e.g. `[gateway]`, `[canvas]`, `[tailscale]`) - **Subsystem prefixes** on every line (e.g. `[gateway]`, `[canvas]`, `[tailscale]`)
- **Subsystem colors** (stable per subsystem) plus level coloring - **Subsystem colors** (stable per subsystem) plus level coloring
- **Color only when TTY** (`process.stdout.isTTY`/`process.stderr.isTTY`), respects `NO_COLOR` - **Color when output is a TTY or the environment looks like a rich terminal** (`TERM`/`COLORTERM`/`TERM_PROGRAM`), respects `NO_COLOR`
- **Sub-loggers by subsystem** (auto prefix + structured field `{ subsystem }`) - **Sub-loggers by subsystem** (auto prefix + structured field `{ subsystem }`)
- **`logRaw()`** for QR/UX output (no prefix, no formatting) - **`logRaw()`** for QR/UX output (no prefix, no formatting)
- **Console styles** (e.g. `pretty | compact | json`) - **Console styles** (e.g. `pretty | compact | json`)
- **Console log level** separate from file log level (file keeps full detail) - **Console log level** separate from file log level (file keeps full detail)
- **WhatsApp message bodies** are logged at `debug` (use `--verbose` to see them)
This keeps existing file logs stable while making interactive output scannable. This keeps existing file logs stable while making interactive output scannable.