An audit trail for Grok Build
Euthyne plugs into Grok Build, xAI's coding agent for the terminal, through its command hooks. Every prompt, shell command, file edit, MCP call and permission denial in an enrolled repository becomes a signed receipt, in the same format as Claude Code.
What Euthyne records for Grok Build
Prompts and tool calls
Prompts, shell commands, file edits and reads, MCP calls, permission denials, subagents and turns become signed receipts. Grok Build runs hooks fail-open: if a hook times out or crashes, the agent carries on and that event has no receipt.
MandatesPartial
Your permission mode, allow, ask and deny rules, sandbox profile and MCP server names are signed as a mandate, from Grok Build's config files and the Claude settings it reads. A repository's .grok/config.toml counts only once you trust the folder. Rules written as [permission] rules tables, and --allow or --deny flags, are not read, so checks under them read unknown. On Team and Company, your org's signed policy decides each tool call on your machine before it runs, offline. Enforced, fails open on timeout: Grok Build runs the call if the hook times out or is killed.
Tokens and costPartial
Tokens in and out, cache reads, model calls and cost, read from the usage file Grok Build keeps for each session on your machine. Receipts from a subagent's own session carry none.
User-level install
--hooks user writes ~/.grok/hooks/euthyne.json, a file of its own, so the hooks run in every project. Only enrolled repositories are recorded.
Repo-level install
--hooks repo writes .grok/hooks/euthyne.json and keeps it out of git. Grok Build runs it once you trust the folder with /hooks-trust.
Content stays with you
Prompts, outputs, commands and file contents are committed as salted hashes before anything leaves your machine.
The Grok Build hooks Euthyne uses
Sessions
SessionStart and SessionEnd open and close the record of each session, and of each subagent's own 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. An ask rule denies.
Tool calls
PostToolUse and PostToolUseFailure record shell commands, file edits and reads, search, web and MCP calls, with their outcome, duration and the files they touch.
Denials
PermissionDenied records each tool call Grok Build's permission rules refused.
Subagents
SubagentStart and SubagentStop record each subagent Grok Build starts.
Turns
Stop, StopFailure and StopCancelled record the end of each turn, whether it finished, failed or you stopped it.
From install to the first Grok Build 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 grok-build
Read the consent text, sign in through your browser and enrol the repository. Init writes the Grok Build hooks to ~/.grok/hooks/euthyne.json. Nothing is recorded before you accept.
Run grok as usual
Hooks in ~/.grok/hooks run without a trust step. With --hooks repo instead, run /hooks-trust once in the repository.
curl -fsSL https://euthyne.com/install | shbrew install euthyne-labs/tap/euthyneeuthyne init --agent grok-build --hooks userCommon questions
Yes. Euthyne records Grok Build today, in the repositories you enrol.
Twelve: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PostToolUseFailure, PermissionDenied, SubagentStart, SubagentStop, Stop, StopFailure, StopCancelled and SessionEnd. Each runs euthyne hook grok-build, and PreToolUse runs euthyne hook grok-build PreToolUse. They never change a tool call, and PreToolUse only blocks one when your org enforces a policy that denies it.
Yes. Grok Build runs hooks fail-open: if a hook times out or crashes, the tool call goes ahead and that event has no receipt. Euthyne gives each hook 30 seconds. A skipped event leaves no mark in the chain.
No. When Grok Build runs the Euthyne hook it found in your Claude Code settings, Euthyne leaves the event to the Grok Build hook, so each event is signed once and names Grok Build.
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 Grok Build's PreToolUse deny, and Grok 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. Grok Build runs the call anyway if the hook times out, so we label it enforced, fails open on timeout.
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 Grok Build checked 23 Oct 2026 against its documentation. Spot something out of date? Write to hello@euthyne.com.
Grok is a trademark of xAI. Euthyne is not affiliated with, endorsed by or sponsored by xAI.
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