codex - 💡(How to fix) Fix Hook execution audit logs clutter session terminal output [1 comments, 2 participants]

What version of Codex CLI is running?

1.109.4

What subscription do you have?

plus

Which model were you using?

gpt-5.4

What platform is your computer?

Darwin 25.3.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Vibeyard/iTerm

What issue are you seeing?

When hooks are configured (e.g., SessionStart and UserPromptSubmit), their execution logs are printed directly into the session terminal output, cluttering the conversation with noise. Each hook invocation produces multiple lines like:

» Running SessionStart hook » Running SessionStart hook » Running SessionStart hook SessionStart hook (completed) SessionStart hook (completed) SessionStart hook (completed) » Running UserPromptSubmit hook » Running UserPromptSubmit hook » Running UserPromptSubmit hook UserPromptSubmit hook (completed) UserPromptSubmit hook (completed) UserPromptSubmit hook (completed)

This appears before every response, even for a simple prompt like "hey". The hook audit log lines are repeated multiple times (3x each in my case, matching the number of configured hooks) and are interleaved with the actual conversation output.

What steps can reproduce the bug?

1. Setup hook.
2. Start a session.
3. Submit a prompt, e.g. "hey"

What is the expected behavior?

Hook execution logs should either be suppressed from the terminal output entirely, shown in a debug/verbose mode only, or at minimum deduplicated and visually separated from the conversation.

Additional information

No response