CLI hook review detail screen has no reject/disable/remove action

What issue are you seeing?

The Codex CLI hook review detail screen for a newly discovered hook only exposes t to trust and esc to go back. There is no visible way to reject, disable, remove, ignore, or open the source config from that screen.

This makes the review flow feel like a binary choice between trusting an untrusted command or backing out without any clear next action. In practice, the user had to inspect the filesystem outside the UI and manually delete the project-local .codex/hooks.json file to remove the hook.

What steps can reproduce the issue?

1. Create a project-local hook config, for example .codex/hooks.json, with a PostToolUse command hook.
2. Start Codex CLI in that project.
3. Open or trigger the hooks review flow for the new hook.
4. Select the hook detail view.
5. Observe the footer/help text.

Observed detail screen:

PostToolUse hooks
1 hook needs review before it can run.

[!] Hook 1 · new

Event     PostToolUse
Matcher   Edit|Write
Source    Project config - ~/workspace/retirement-readiness/.codex/hooks.json
Command   f=$(jq -r '.tool_input.file_path // empty'); ...
Timeout   600s
Trust     New hook - review required

Press t to trust; esc to go back

What is the expected behavior?

The hook review detail screen should provide clear actions for the common decisions a user can make after reviewing an untrusted hook, for example:

• Trust once / trust this hook
• Trust all matching hooks, if available in the parent flow
• Reject or continue without trusting
• Disable this hook
• Open/copy the source config path
• Show the full command in a readable/copyable view
• Link to hook documentation

At minimum, the UI should tell the user exactly how to remove or disable the hook when they do not want to trust it.

Why this matters

Hooks can run commands outside the normal agent flow after being trusted. The trust review UI is the security-critical moment where users decide whether a command is acceptable. A screen with only trust and go back leaves the non-trust path unclear and pushes users into manual filesystem debugging.

Environment

• Codex CLI: codex-cli 0.141.0
• Platform: macOS
• Hook source: project config, .codex/hooks.json
• Event shown: PostToolUse

Additional information

Related but not identical existing issues include hook trust and TUI hook behavior reports such as #22847 and #24093. This report is specifically about the hook review detail screen lacking an explicit reject/disable/remove path and making esc ambiguous.