Skip to content

Force hook usage approval with config #17422

Open

Description

@Frulfump

Seems dangerous otherwise

Activity

  1. added
    enhancementNew feature or request
    CLIIssues related to the Codex CLI
    hooksIssues related to event hooks
    on Apr 11, 2026
  2. github-actions commented on Apr 11, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  3. etraut-openai commented on Apr 11, 2026

    @etraut-openai
    Contributor

    Can you say more about what you're looking for? Are you saying that you think that all hooks should be gated by a master configuration switch?

  4. Frulfump commented on Apr 11, 2026

    @Frulfump
    Author

    Can you say more about what you're looking for? Are you saying that you think that all hooks should be gated by a master configuration switch?

    Sure, yes the second part there. So that I'm forced to approve hooks usage at least the first time it wants to run.

  5. oxysoft commented on May 8, 2026

    @oxysoft

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthooksIssues related to event hooks

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions