Skip to main content
reopt Handbook
reopt Handbook
Codex Command MasterLabels and command selectionHow to read a detail guideComplete command listTerminal CLI Commands and Options

Task guides

Core Command GroupSession Command GroupCustom Command GuideMCP Command and Integration GuideDesign Workflows

Conversation and context

Cmd. /clearCmd. /renameCmd. /archiveCmd. /deleteCmd. /compactCmd. /copyCmd. /memoriesCmd. /importCmd. /initCmd. /mentionCmd. /forkCmd. /sideCmd. /resumeCmd. /newCmd. /cdCmd. /exportCmd. /recap

Planning and execution

Cmd. /planCmd. /goalCmd. /psCmd. /stopCmd. /app

Review and verification

Cmd. /review

Models and settings

Cmd. /modelCmd. /fast

Permissions and integrations

Cmd. /permissionsCmd. /ideCmd. /setup-default-sandboxCmd. /sandbox-add-read-dirCmd. /pluginsCmd. /hooksCmd. /approveCmd. /skillsCmd. /mcp

Status and diagnostics

Cmd. /agentCmd. /appsCmd. /diffCmd. /feedbackCmd. /personalityCmd. /rawCmd. /statusCmd. /debug-configCmd. /title

Display and input

Cmd. /keymapCmd. /vimCmd. /experimentalCmd. /statuslineCmd. /themeCmd. /petsCmd. /voiceCmd. /worktree

Account and usage

Cmd. /exitCmd. /logoutCmd. /quitCmd. /usage

Legacy

Cmd. /approvals

Verification and history

Current verification scopeHandbook updatesRelease coverage historyEarlier verification recordsCommand change history
Handbook›Codex Command Master›Cmd. /hooks
한국어English

Cmd. /hooks

Review lifecycle hooks and manage trust or disabled state.

Key takeaways

  • Review lifecycle hooks and manage trust or disabled state.
  • Check the input surface and availability before using the examples below.

Purpose

Review lifecycle hooks and manage trust or disabled state.

/hooks

Availability

FieldValue
Input surfaceRunning CLI prompt
KindBuilt-in
StatusCurrent reference
Aliases—
Documented minimumNot specified
Reviewed against2026-09-22 · Codex CLI 0.155.1

The installed command menu and account or organization settings determine availability.

Examples

/hooks

When to use it

  1. Run /hooks after adding .codex/hooks.json or inline [hooks] config to verify source and trust state.
  2. Before enabling plugin-bundled hooks, check /plugins for plugin state and /hooks for actual hook behavior.
  3. Record which hooks are managed by policy and which are local project hooks.

Choosing related commands

CommandDifferenceChoose It When
/hooksReviews hook sources and trust stateHooks may run before, during, or after turns
/pluginsShows plugin inventory and bundled hooksYou need to know where a hook came from
/debug-configExplains config layersYou need precedence and policy diagnostics

Effects and persistence

Shows configured hooks and their triggers. Editing a hook changes what runs when its event occurs.

/hooks opens the hook browser so you can inspect configured lifecycle hooks, trust new or changed hooks, and disable individual non-managed hooks before they run.

to 0.150.0 Update

  • Hook commands can run asynchronously and invoke MCP tools.
  • The 0.150.0 changelog says Interrupt fires when the active top-level turn is interrupted and can run command or MCP handlers. It is narrower than “any child task stopped” and distinct from a normal Stop event.

Do not invent an Interrupt schema yet

The current Hooks reference still omits Interrupt from its supported-event tables. Track it as a 0.150.0 release feature, but do not publish a copied JSON/TOML event shape until the reference adds the contract. Use /hooks to review the exact hook loaded by the installed build.

Cautions

Core events to inspect include PreToolUse, PermissionRequest, PostToolUse, UserPromptSubmit, and Stop, configured through .codex/hooks.json or inline [hooks]. Managed hooks and hooks from an untrusted project have different controls.

  • Managed hooks are trusted by policy and cannot be disabled from the user hook browser.
  • Project-local hooks load only when the project .codex/ layer is trusted.
  • User approval of a project hook is tied to the exact content hash; review and trust it again after a change.
  • MCP hook handlers reuse an existing connection, run synchronously, cannot request approval, and do not trigger other hooks. Treat auth and availability failures as a separate failure path.
  • Hooks are guardrails, but they are not a complete enforcement boundary for every shell or tool path.

Official sources

  • Developer Commands
  • Hooks
  • Changelog

Complete command list · Verification scope · History for this command

Related docs

Cmd. /hooks

Claude Code Command Master · Shows configured hooks and their triggers. Editing a hook changes what runs when its event occurs.

Hooks

Claude Code Complete Guide · Use Claude Code hooks for predictable automation and repository guardrails.

Ch11. Schedules, State, Hooks

Enterprise Eve Agent Development · Connect Eve cron schedules, durable state, and stream-event hooks to automation, memory, and audit.

Cmd. /update-config

Claude Code Command Master · Use the Claude Code bundled skill to edit the appropriate settings.json from a requested permission, environment, or hook change.

Case: OpenAI

Harness Engineering · Analyze OpenAI's harness view through repo-readability, observability, sandboxing, runtime surface, and cleanup.

Cmd. /plugins

Browse installed and discoverable Codex plugins.

Cmd. /approve

Approve one retry of a recent auto-review denial.

On this page

PurposeAvailabilityExamplesWhen to use itChoosing related commandsEffects and persistenceto 0.150.0 UpdateCautionsOfficial sources