[codex] Improve hook status rendering

[abhinav-oai]

Motivation

Make hook display less noisy and more useful by keeping transient hook activity out of permanent history unless there is useful output

Also addresses some of the concerns in #15497

Changes

Hook Lifecycle Rendering

• Hook start events no longer write permanent history rows like Running PreToolUse hook.
• Running hooks now render in a dedicated live hook area above the composer. It's similar to the active cell we use for tool calls but its a separate lane.
• Running hook rows use the existing animation setting.

Hook Reveal Timing

• We wait 300ms before showing running hook rows and linger for up to 600ms once visible.
  • This is so fast hooks don't flash a transient Running hook row before user can read it every time.
• If a fast hook completes with meaningful output, only the completed hook result is written to history.
• If a fast hook completes successfully with no output, it leaves no visible trace.

Completed Hook Output

• Completed hooks with output are sticky, for example • SessionStart hook (completed).
• Hook output entries are rendered under that row with stable prefixes: warning:, stop:, feedback:, hook context:, and error:.
• Blocked hooks show feedback entries, for example • PreToolUse hook (blocked) followed by feedback: ....
• Failed hooks show error entries, for example • PostToolUse hook (failed) followed by error: ....
• Stopped hooks show stop entries and remain visually treated as non-success.

Parallel Hook Behavior

• Multiple simultaneously running hooks can be tracked in one live hook cell.
• Adjacent running hooks with the same hook event name and same status message collapse into a count, for example • Running 3 PreToolUse hooks: checking command policy.
• Running hooks with different event names or different status messages remain separate rows.

Hook Run Identity

• PreToolUse and PostToolUse hook run IDs now include the tool call ID which prevents concurrent tool-use hooks from sharing a run ID and clobbering each other in the UI.
• This ID scoping applies to tool-use hooks only; other hook event types keep their existing run identity behavior.

App-Server Hook Notifications

• App-server HookStarted and HookCompleted notifications use the same live hook rendering path as core hook events.
• UserPromptSubmit hook notifications now render through the same completed hook output format, including warning and stop entries.

[abhinav-oai]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 22490e9ba5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[abhinav-oai]

@codex review

[abhinav-oai]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2a8e2ae1be

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[fcoury-oai]

The code looks good, I was able to test it and it works great, aside from one finding below and the one that Codex already pin pointed.

[fcoury-oai]

Looks good! Approved.