Command escalation information look to be not available in Codex hooks

[patatoid]

What version of Codex CLI is running?

0.139.0

What subscription do you have?

Pro 5x

Which model were you using?

gpt-5.5 medium

What platform is your computer?

Linux 6.12.90+deb13.1-amd64 x86_64 unknown

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

neovim

Codex doctor report

What issue are you seeing?

The escalated command was approved and executed successfully. From the hook side, escalation does not seem available or enforceable enough to distinguish this from other command authorization cases.

What steps can reproduce the bug?

Uploaded thread: 019ec28d-72b9-7d10-8f21-0f4f32c88dba

What is the expected behavior?

Hook payloads should expose escalation state and target command details in a way that allows a hook to make an enforceable decision before the command runs. If a hook returns a block decision, the escalated operation should not execute.

Additional information

I encountered the issue while working on a hook malach-it/boruta-server#163, I am discovering hooks then I may be wrong, sorry if it is the case.

Thank you for your work on Codex

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• PreToolUse deny (exit 2 + permissionDecision JSON) is not enforced for apply_patch - hook fires, write proceeds #27833
• Codex Desktop exposes no-op functions.zz tool that is accidentally selected and cannot be denied #27342

Powered by Codex Action

[patatoid]

A rephrase suggestion from Codex

Command escalation appears to surface to Codex’s approval system, and hooks have a PermissionRequest lifecycle event, but the hook documentation does not clearly define whether escalation metadata is available to hooks in a stable payload field. This makes it hard for policy hooks to reliably distinguish normal command execution from sandbox-escalated command execution.