Skip to content

Surface config parse errors to stderr - #115

Merged
jhrozek merged 1 commit into
mainfrom
fix/surface-config-parse-errors
Apr 10, 2026
Merged

Surface config parse errors to stderr#115
jhrozek merged 1 commit into
mainfrom
fix/surface-config-parse-errors

Conversation

@JAORMX

@JAORMX JAORMX commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Config parse errors for both global (~/.config/broodbox/config.yaml) and per-workspace (.broodbox.yaml) files were only logged to the slog file logger, which users never see unless they manually inspect broodbox.log
  • This caused silent fallback to empty defaults when the config file had YAML syntax errors (e.g. a missing # on a comment line), making it appear as if settings like cpus and memory were being ignored
  • Now prints a warning to stderr with the file path and error message so users get immediate feedback

Test plan

  • Introduce a YAML syntax error in ~/.config/broodbox/config.yaml and run bbox claude-code — verify warning is printed to stderr
  • Introduce a YAML syntax error in a workspace .broodbox.yaml and run bbox claude-code — verify warning is printed to stderr
  • Run with a valid config — verify no spurious warnings appear

🤖 Generated with Claude Code

Config parse errors were only logged to the log file via slog, which
users never see unless they manually inspect broodbox.log. This caused
silent fallback to empty defaults when the config file had YAML syntax
errors, making it appear as if settings were being ignored.

Print a warning to stderr for both global and per-workspace config
parse failures so users get immediate feedback.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@jhrozek
jhrozek merged commit 419c62e into main Apr 10, 2026
8 checks passed
@jhrozek
jhrozek deleted the fix/surface-config-parse-errors branch April 10, 2026 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants