Feature request: expose a hook for request_user_input

Feature request: expose a hook for request_user_input

What would you like to see?

Please expose a lifecycle hook/event when Codex presents a structured request_user_input prompt to the user (for example, a form with questions and selectable options).

Why is this useful?

Users may be away from the screen while Codex is waiting for an answer. A dedicated hook would allow integrations to provide an accessible notification, such as macOS text-to-speech, a desktop notification, or a remote alert.

This should be distinct from PermissionRequest: an approval request is a security/authorization event, while request_user_input is a normal conversational decision point.

Proposed behavior

Add a documented hook event, for example UserInputRequest or RequestUserInput, containing safe metadata such as:

• the number of questions/options;
• a short, sanitized summary or title;
• session/thread identifier if available.

The hook should run when the prompt becomes available to the user, without exposing sensitive field values by default.

Example configuration:

[hooks]
RequestUserInput = [
  { matcher = "", hooks = [
    { type = "command", command = "say 'Codex precisa de uma resposta'", async = true },
  ] },
]

Alternatives considered

Using PermissionRequest is not appropriate because it is not emitted for normal user-input forms and represents a different interaction. Monitoring terminal/UI output would be fragile and would not work consistently across Codex clients.

Environment

• macOS
• Codex CLI/Desktop
• Global hooks configuration

Start by tracing the existing PermissionRequest hook and the request_user_input lifecycle in Codex CLI/Desktop. Define where the new documented hook becomes available, what safe metadata it carries, and how global hooks configuration invokes it without exposing sensitive field values.