Hook support not working in IDE extension and Codex app

Resolved 💬 4 comments Opened Apr 16, 2026 by Zeoy2020 Closed Apr 16, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.409.61251

What subscription do you have?

null

What platform is your computer?

windows

What issue are you seeing?

Although maintainers mentioned that hook support is already implemented for the IDE extension and Codex app, I cannot get it to work. The CLI hooks behave correctly, but the same functionality does not trigger in the IDE extension or Codex app.

What steps can reproduce the bug?

config.toml
[features]
codex_hooks = true

hooks.json
"hooks": {
"PostToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "xxxx'"
}
]
}
]
}

Agent environment:Windows Native
Integrated terminal shell:PowerShell

Actual behavior:
(When using hooks, my scripts will print some logs on txt)
CLI: hook executes as expected.
IDE extension: hook is ignored.
Codex app: hook is ignored.

What is the expected behavior?

Hooks should execute consistently across CLI, IDE extension, and Codex app.

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 4 months ago

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

  • ##17930

Powered by Codex Action

Zeoy2020 · 4 months ago

I tried on 3 different machines(windows), all show the same behavior

etraut-openai contributor · 4 months ago

This is because hooks were only recently enabled for Windows in the CLI. The version of the CLI that was included in your version of the IDE and app does not yet support it. The next releases will.

oxysoft · 3 months ago

Indexed this hook ticket in the umbrella tracker: #21753

Goal: collect the scattered Codex hook requests and bugs into one parity matrix for Full Claude Code Hook Parity (29+), while preserving this issue as the detailed thread for its specific behavior.