codex - 💡(How to fix) Fix Allow Codex hooks to run silently without rendering completed hook entries [1 comments, 2 participants]

TL;DR

Adding a hook-level option like "silent": true or a global Codex setting to hide successful hook lifecycle entries could resolve the issue of excessive visible UI entries for successful hooks.

Guidance

• Consider implementing a hook-level option to suppress status updates for successful hooks with no output, such as "silent": true or "suppressStatus": true.
• Alternatively, explore modifying the rendering logic to only display hook entries when the hook writes output, blocks an action, or fails.
• Evaluate the feasibility of introducing a global Codex setting to hide successful hook lifecycle entries, providing a centralized control for managing UI noise.

Example

No code snippet is provided as the issue focuses on feature requests and UI behavior rather than specific code implementation.

Notes

The solution may require modifications to the Codex hooks system and its interaction with the UI, which could involve significant development and testing efforts. The exact implementation details are not specified in the issue.

Recommendation

Apply a workaround by introducing a hook-level option like "silent": true to suppress status updates for successful hooks, as this approach seems to directly address the reported issue with minimal disruption to existing functionality.