LIVENative hooks, ten events

An audit trail for Codex

Euthyne plugs into Codex through its own hooks. Every prompt, shell command, patch, MCP call and approval request in an enrolled repository becomes a signed receipt, in the same format as Claude Code. With an org policy, the hook also decides each call before it runs.

What Euthyne records

What Euthyne records for Codex

Prompts and tool calls

Prompts, Bash commands, apply_patch edits with every file they touch, MCP calls, approval requests, subagents and turns become signed receipts. Content stays on your machine as salted hashes.

MandatesPartial

The approval policy and sandbox Codex actually ran with are read from the session file and signed. Your execpolicy prefix_rule rules are kept as text in the mandate but not evaluated yet. On Team and Company, your org's signed policy decides each Bash, apply_patch and MCP call on your machine before it runs. Enforced, fails open on timeout: Codex runs the call if the hook times out, crashes or is not trusted yet.

Tokens and costPartial

Tokens in and out for each turn, read from the Codex session file on your machine. Codex reports no cost, so receipts carry none.

User-level install

--hooks user writes ~/.codex/hooks.json so the hooks run in every project. Codex runs a new hook only once you trust it in /hooks.

Repo-level install

--hooks repo writes .codex/hooks.json in the repository. Start codex there once, open /hooks and trust the Euthyne hooks.

Content stays with you

Prompts, outputs, commands and file contents are committed as salted hashes before anything leaves your machine.

Hook events

The Codex hooks Euthyne uses

Sessions

SessionStart and SessionEnd open and close the record of each session.

Prompts

UserPromptSubmit records each prompt, with its text kept as a salted hash.

Policy decisions

PreToolUse checks each call against your org's signed policy, when it has one, and signs the decision. Codex hooks can only deny, so an ask rule denies.

Tool calls

PostToolUse records Bash, apply_patch and MCP calls, with their outcome and the files a patch touches.

Approvals

PermissionRequest records each time Codex asks before it runs something.

Subagents

SubagentStart and SubagentStop record each subagent Codex starts.

Turns

Stop and Interrupt record the end of each turn, whether it finished or you stopped it.

Install

From install to the first Codex receipt

  1. Install the CLI

    With curl or Homebrew, on macOS or Linux. The script checks the release against its checksums and installs to ~/.local/bin.

  2. euthyne init --agent codex

    Read the consent text, sign in through your browser and enrol the repository. Init writes the Codex hooks. Nothing is recorded before you accept.

  3. Trust the hooks once

    Start codex in the repository, open /hooks and trust the Euthyne hooks. codex exec skips hooks you have not trusted.

Install script
curl -fsSL https://euthyne.com/install | sh
Homebrew
brew install euthyne-labs/tap/euthyne
Set up Codex
euthyne init --agent codex
FAQ

Common questions

Yes. Euthyne records Codex today, in the repositories you enrol.

Ten: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PermissionRequest, SubagentStart, SubagentStop, Stop, Interrupt and SessionEnd. Each runs euthyne hook codex.

Codex runs a new hook only after you trust it in /hooks. Until you do, Codex skips the Euthyne hooks and nothing is recorded. You do it once per hooks file.

No. Euthyne reads tokens from the Codex session file on your machine, and Codex does not report cost there, so Codex receipts carry tokens without a cost.

Bash rules see through plain NAME=value assignments, quoting and a fixed set of wrappers whose flags Euthyne models, such as env, sudo, timeout, nice and sh -c. Anything else in front of the command, like an unknown wrapper or flag, a redirection, eval, a variable or a glob as the command, or a shell reading stdin, is treated as undecidable, so an enforced policy blocks it unless your org chose otherwise.

Only if your org publishes an enforced policy, on Team and Company, and only once you trust the hooks. A new policy starts in dry run: decisions are signed into receipts and nothing is blocked. Once enforced, a denied call is blocked through Codex's PreToolUse deny, and Codex is told the rule id and its reason, never the policy. Codex runs the call anyway if the hook times out or crashes, so we label it enforced, fails open on timeout.

Related

Where to go next

Facts about Codex checked 18 Oct 2026 against its documentation. Spot something out of date? Write to hello@euthyne.com.

OpenAI and Codex are trademarks of OpenAI. Euthyne is not affiliated with, endorsed by or sponsored by OpenAI.

Every action.
On the record.

Euthyne is in public beta. Leave your email and we'll reach out, or install the CLI and read the quickstart.

Install script
curl -fsSL https://euthyne.com/install | sh
Homebrew
brew install euthyne-labs/tap/euthyne
Read the quickstart
Euthyne
EuthyneBordeaux