Not normative. Thin adapter that reuses the six hook scripts from
../hooks-claude-code/hooks/and registers them against Codex's tool / command surface.
| File | Purpose |
|---|---|
settings.example.json |
Merge into your Codex hook config |
hooks.example.json |
Opt-in Codex plugin-style hook example; not loaded by default |
adapter/parse-event.sh |
Codex event → AP_* env vars |
DEVIATIONS.md |
Codex-specific quirks vs. the contract |
Hook scripts are not duplicated here. Each registered command shells
out to ../hooks-claude-code/hooks/<name>.sh.
These hooks are opt-in. The repository's .codex-plugin/plugin.json
intentionally does not point at a root hooks.json, because the
reference hooks may block git commit or warn on git push until a
project has adopted Change Manifest and evidence artifacts.
- Locate the settings file your Codex install reads on startup.
- Merge
settings.example.jsoninto it. Adjust key names to the Codex version's schema — keep the commands and their ordering. - Confirm the relative path resolves from the working directory Codex uses when spawning hook commands; prefer absolute paths for installs outside the repo root.
If your Codex install supports plugin-local hook files, copy
hooks.example.json to the hook path your install expects only after
you intentionally choose to enable the checks.
Hooks read from git and $AGENT_PROTOCOL_MANIFEST_PATH, not from a
Codex event payload, so no translation is required for the four
reference hooks. adapter/parse-event.sh exposes cross-runtime
AP_* env vars for future payload-aware hooks.
../hooks-claude-code/README.md— canonical install guide.DEVIATIONS.md— Codex-specific deviations.../../docs/runtime-hook-contract.md— capability contract (normative).