codex - 💡(How to fix) Fix Add hook_report_level config to suppress routine hook chatter [2 comments, 2 participants]

hook_report_level = "off" | "error" | "warn" | "all"

• warn (default): suppress HookStarted; drop context entries; suppress empty “completed” hook blocks
• error: only show hook completions when status is failed/blocked/stopped (and only error/stop/feedback entries)

TL;DR

Add a hook_report_level config knob to control the verbosity of hook notifications, allowing users to suppress non-actionable output.

Guidance

• Review the proposed hook_report_level config options (off, error, warn, all) to determine which level best suits your needs.
• Test the warn default setting to see if it effectively suppresses unnecessary notifications, such as HookStarted and empty completed hook blocks.
• Consider trying the error setting to only show hook completions when the status is failed, blocked, or stopped.
• Evaluate the implementation in the xsyetopz:fix/hook-report-level fork branch and commit a8133b308 to ensure it meets your requirements.

Example

No explicit code example is provided, but the proposed hook_report_level config knob can be used as follows:

hook_report_level = "warn"

This would suppress HookStarted notifications and drop context entries, while still showing error and warning messages.

Notes

The proposed solution only filters user-facing hook notifications and does not affect the execution of hooks or the injection of additional context into the model prompt.

Recommendation

Apply the workaround by adding the hook_report_level config knob and setting it to the desired level (e.g., warn or error), as this allows for more control over the verbosity of hook notifications.