LIVENative hooks, ten events

An audit trail for Claude Code

Euthyne plugs into Claude Code through its own hooks. Every prompt, tool call, permission denial and session event in an enrolled repository becomes a signed receipt. With an org policy, the hook also decides each tool call before it runs.

What Euthyne records

What Euthyne records for Claude Code

Prompts and tool calls

Prompts, tool calls, MCP tools, denials, subagents and turns become signed receipts. Content stays on your machine as salted hashes.

Mandates

Your allow, ask and deny rules, the permission mode and the MCP server lists are signed as a mandate, and each action is checked against them. On Team and Company, your org's signed policy decides each tool call on your machine before it runs, offline. Enforced: the hook is installed so that a crash or timeout blocks the call too.

Tokens and cost

Tokens in and out, cache reads and writes, cost and API time, from Claude Code's own telemetry. Opt-in at setup, read on 127.0.0.1 only.

User-level install

--hooks user writes your user settings, with a backup, so the hooks run in every project. Only enrolled repositories are recorded.

Repo-level install

--hooks repo writes .claude/settings.local.json and keeps it out of git.

Content stays with you

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

Hook events

The Claude Code 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 tool call against your org's signed policy, when it has one, and signs the decision. It records nothing without a policy.

Tool calls

PostToolUse and PostToolUseFailure record every tool, its outcome and duration, MCP tools included.

Denials

PermissionDenied records the actions Claude Code refused under your rules.

Subagents

SubagentStart and SubagentStop record each subagent, with its agent ID and type.

Turns

Stop records the end of each turn, with the last assistant message as a salted hash.

Install

From install to the first Claude Code 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

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

  3. Work as usual

    Use Claude Code. Receipts are signed on each event and synced in the background. euthyne uninstall removes exactly what init wrote.

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

Common questions

Yes. Euthyne records Claude Code today, in the repositories you enrol.

Without an org policy, the PreToolUse hook returns at once and records nothing. With one, it decides from the signed policy cached on your machine, with no network call. The hook always exits 0 and writes to stdout only to deny or ask. Receipts sync in the background.

Ten: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PostToolUseFailure, PermissionDenied, SubagentStart, SubagentStop, Stop and SessionEnd. Each runs euthyne hook claude-code.

No. It records only after you accept the consent text, on an enrolled device, in a repository you enrolled. With user-level hooks, other repositories are skipped.

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. A new policy starts in dry run: decisions are signed into receipts and nothing is blocked. Once enforced, a denied call is blocked through Claude Code's PreToolUse deny, and Claude is told the rule id and its reason, never the policy. If the policy can't be evaluated, the call is denied unless your org chose otherwise.

Related

Where to go next

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

Claude and Claude Code are trademarks of Anthropic, PBC. Euthyne is not affiliated with, endorsed by or sponsored by Anthropic.

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