An audit trail for Hermes Agent
Euthyne plugs into Hermes Agent through the shell hooks in its config.yaml. Every prompt, terminal command, file edit, MCP call and subagent in an enrolled repository becomes a signed receipt, in the same format as Claude Code.
What Euthyne records for Hermes Agent
Prompts and tool calls
Prompts, tool calls with their status and duration (terminal, write_file, patch, MCP and the rest), the files an edit touches, subagents and turns become signed receipts. Content stays on your machine as salted hashes.
MandatesPartial
The mandate carries a salted hash of your Hermes config.yaml, so you can show which configuration was in force. Hermes approval settings are not read yet, so tool checks read unknown. On Team and Company, your org's signed policy decides each tool call on your machine before it runs, offline. Enforced: the pre_tool_call hook is installed with fail_closed, so a crash or timeout blocks the call too, once you approve the hook.
Tokens and costNo
Hermes passes no token counts or cost to shell hooks, so Hermes receipts carry none.
User-level install
euthyne init --agent hermes adds the hooks block to ~/.hermes/config.yaml, or to $HERMES_HOME/config.yaml. Hermes runs a new hook only once you approve it.
Repo-level installNo
Hermes reads hooks only from its own config.yaml, so there is no per-repository install.
Content stays with you
Prompts, outputs, commands and file contents are committed as salted hashes before anything leaves your machine.
The Hermes Agent hooks Euthyne uses
Sessions
on_session_start and on_session_finalize open and close the record of each session.
Prompts
pre_llm_call records each prompt, with its text kept as a salted hash.
Policy decisions
pre_tool_call checks each tool call against your org's signed policy, when it has one, and signs the decision. An ask rule denies.
Tool calls
post_tool_call records terminal commands, file edits and MCP calls, with their outcome, duration and the files they touch.
Subagents
subagent_start and subagent_stop record each subagent Hermes delegates to.
Turns
on_session_end records the end of each turn, whether it finished or was interrupted.
From install to the first Hermes Agent receipt
Install the CLI
With curl or Homebrew, on macOS or Linux. The script checks the release against its checksums and installs to ~/.local/bin.
euthyne init --agent hermes
Read the consent text, sign in through your browser and enrol the repository. Init adds the Euthyne hooks to your Hermes config.yaml. Nothing is recorded before you accept.
Approve the hooks once
Start hermes chat in a terminal and approve each Euthyne hook when it asks, or run hermes --accept-hooks chat once. The gateway and cron skip hooks you have not approved.
curl -fsSL https://euthyne.com/install | shbrew install euthyne-labs/tap/euthyneeuthyne init --agent hermesCommon questions
Yes. Euthyne records Hermes Agent today, in the repositories you enrol.
Eight: on_session_start, pre_llm_call, pre_tool_call, post_tool_call, subagent_start, subagent_stop, on_session_end and on_session_finalize. Each runs euthyne hook hermes, and pre_tool_call runs euthyne hook hermes pre_tool_call with fail_closed and a 20 second timeout. Only pre_tool_call can block a tool call, and only when your org enforces a policy that denies it.
Hermes runs a new shell hook only after you approve it, and keeps your approvals in shell-hooks-allowlist.json. Until you do, Hermes skips the Euthyne hooks and nothing is recorded.
No. Hermes does not pass token counts or cost to shell hooks, so Hermes receipts carry the model and the actions but no usage.
Only if your org publishes an enforced policy, on Team and Company, and only once you approve the hook. A new policy starts in dry run: decisions are signed into receipts and nothing is blocked. Once enforced, a denied call is blocked through Hermes's pre_tool_call block, and Hermes is told the rule id and its reason, never the policy. Shell, file reads and writes, web and MCP calls are matched against the same rules as Claude Code, so a rule like Bash(git push:*) applies here too; other known tools are decided under their own names. Tools Euthyne does not know yet, and MCP calls that do not name an exact server and tool, are denied while a policy is enforced. The hook is installed with fail_closed, so Hermes also blocks the call if the hook times out or crashes.
No. Prompts, outputs, commands and file contents are hashed with salts that stay with you, before anything leaves your machine. Euthyne sees who acted, with which agent and model, and when, never what was said.
Not for the record itself. Each receipt is signed at the source and added to an append-only log whose checkpoints are anchored on-chain. Alter or delete one and verification fails, for anyone who runs euthyne verify, with no account needed. Agent and organization identities are W3C Verifiable Credentials.
Where to go next
Facts about Hermes Agent checked 23 Oct 2026 against its documentation. Spot something out of date? Write to hello@euthyne.com.
Hermes Agent is a trademark of its owner. Euthyne is not affiliated with, endorsed by or sponsored by Nous Research.
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.
curl -fsSL https://euthyne.com/install | shbrew install euthyne-labs/tap/euthyne