codex - 💡(How to fix) Fix Hook support not working in IDE extension and Codex app [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18090Fetched 2026-04-17 08:33:04
View on GitHub
Comments
3
Participants
3
Timeline
9
Reactions
0
Author
Timeline (top)
labeled ×4commented ×3closed ×1unlabeled ×1
RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

The issue with hooks not working in the IDE extension and Codex app may be due to a configuration or compatibility issue, and verifying the hook configuration and environment settings is necessary.

Guidance

  • Check the config.toml file to ensure that codex_hooks is set to true and that the file is being read correctly by the IDE extension and Codex app.
  • Verify that the hooks.json file is in the correct location and has the correct syntax, and that the PostToolUse hook is correctly defined.
  • Consider testing the hooks with a different shell, such as Bash, to see if the issue is specific to PowerShell.
  • Check the documentation for the Codex App and IDE extension to ensure that hooks are supported and configured correctly.

Example

No code snippet is provided as the issue seems to be related to configuration and compatibility rather than code.

Notes

The issue may be specific to the Windows platform or the PowerShell shell, and further testing may be necessary to determine the root cause.

Recommendation

Apply workaround: Try testing the hooks with a different shell or environment to see if the issue is specific to the current configuration. This may help to isolate the problem and determine the best course of action.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING