[Feature Request] Add GUI support for deleting hooks in Codex macOS app

Open 💬 1 comment Opened Jun 16, 2026 by singularitti

What variant of Codex are you using?

macOS app

What feature would you like to see?

Please add a GUI mechanism to permanently delete one or more hooks from the Codex macOS application, rather than only allowing users to enable or disable them.

Current Behavior

In the macOS app, navigating to:

Settings → Coding → Hooks → From Config → User config

opens a window that displays hooks imported from:

~/.codex/hooks.json

The UI currently allows hooks to be enabled or disabled, but there is no way to delete them.

Problem

When a hook is no longer needed, users must manually edit configuration files on disk:

  1. Remove the corresponding hook definition from ~/.codex/hooks.json
  2. Remove the associated state entries from ~/.codex/config.toml under [hooks.state]

This process is inconvenient, error-prone, and requires users to understand Codex’s internal configuration structure.

Additionally, deleting hooks from hooks.json does not automatically clean up stale entries in config.toml, leaving orphaned state records behind.

Requested Functionality

Add support in the Hooks UI for:

  • Deleting a single hook.
  • Selecting and deleting multiple hooks at once.
  • Confirmation dialog before deletion.
  • Automatic refresh of the hook list after deletion.

Expected Behavior

When a user deletes a hook through the GUI:

  1. The corresponding hook definition should be removed from ~/.codex/hooks.json
  2. Any associated entries under [hooks.state] in ~/.codex/config.toml should also be removed automatically.
  3. If a deleted hook is the last remaining entry, Codex should clean up any now-unused hook state entries rather than leaving stale configuration behind.

This would significantly improve the hook management experience and prevent users from having to manually maintain multiple configuration files.

Additional information

  • App version: 26.611.61049

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗