Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix False deprecation warning: [features].codex_hooks when using [features].hooks

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…

Codex CLI v0.129.0 shows a deprecation warning on every session start:

[features].codex_hooks is deprecated. Use [features].hooks instead.
Enable it with --enable hooks or [features].hooks in config.toml.

However, config.toml already uses the correct key:

[features]
hooks = true

There is no codex_hooks key anywhere in:

  • ~/.codex/config.toml
  • Project-level .codex/config.toml
  • Environment variables
  • Codex Desktop app Preferences

The warning appears to be a false positive. The binary has an internal feature flag named codex_hooks (found via strings in the native binary at @openai/codex-darwin-arm64), and the deprecation check may be triggering on the internal flag name rather than the actual config key.

Root Cause

Codex CLI v0.129.0 shows a deprecation warning on every session start:

[features].codex_hooks is deprecated. Use [features].hooks instead.
Enable it with --enable hooks or [features].hooks in config.toml.

However, config.toml already uses the correct key:

[features]
hooks = true

There is no codex_hooks key anywhere in:

  • ~/.codex/config.toml
  • Project-level .codex/config.toml
  • Environment variables
  • Codex Desktop app Preferences

The warning appears to be a false positive. The binary has an internal feature flag named codex_hooks (found via strings in the native binary at @openai/codex-darwin-arm64), and the deprecation check may be triggering on the internal flag name rather than the actual config key.

Code Example

[features].codex_hooks is deprecated. Use [features].hooks instead.
Enable it with --enable hooks or [features].hooks in config.toml.

---

[features]
hooks = true
RAW_BUFFERClick to expand / collapse

Description

Codex CLI v0.129.0 shows a deprecation warning on every session start:

[features].codex_hooks is deprecated. Use [features].hooks instead.
Enable it with --enable hooks or [features].hooks in config.toml.

However, config.toml already uses the correct key:

[features]
hooks = true

There is no codex_hooks key anywhere in:

  • ~/.codex/config.toml
  • Project-level .codex/config.toml
  • Environment variables
  • Codex Desktop app Preferences

The warning appears to be a false positive. The binary has an internal feature flag named codex_hooks (found via strings in the native binary at @openai/codex-darwin-arm64), and the deprecation check may be triggering on the internal flag name rather than the actual config key.

Steps to Reproduce

  1. Set [features] hooks = true in ~/.codex/config.toml
  2. Start a Codex CLI session
  3. Warning appears

Expected Behavior

No deprecation warning when using the correct [features].hooks key.

Environment

  • Codex CLI: v0.129.0
  • Platform: macOS (darwin-arm64)
  • Installed via: npm install -g @openai/codex

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

codex - 💡(How to fix) Fix False deprecation warning: [features].codex_hooks when using [features].hooks