An audit trail for Gemini CLI
Euthyne plugs into Gemini CLI through the hooks in its settings.json. Every prompt, shell command, file edit, MCP call and turn in an enrolled repository becomes a signed receipt, in the same format as Claude Code. Google's site says Antigravity CLI replaced Gemini CLI for unpaid and Google One users in June 2026.
What Euthyne records for Gemini CLI
Prompts and tool calls
Prompts, shell commands, file writes and edits with the files they touch, reads, web searches, MCP calls and turns become signed receipts. Content stays on your machine as salted hashes.
MandatesPartial
Your tools.allowed, tools.exclude and tools.confirmationRequired lists and MCP server names are read from the settings.json files Gemini CLI loads and signed. Bare tool names are checked, in a folder Gemini CLI trusts; command prefixes and Policy Engine rules are not yet. Gemini CLI does not tell hooks its approval mode, so receipts name none. 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: Gemini CLI runs the call if the hook times out or is killed.
Tokens and costPartial
Tokens in, cached and out for each turn, read from the Gemini CLI session file on your machine. Gemini CLI reports no cost there, so receipts carry none.
User-level install
--hooks user writes ~/.gemini/settings.json, or the one under GEMINI_CLI_HOME, so the hooks run in every project.
Repo-level install
--hooks repo writes .gemini/settings.json in the repository and keeps it out of git. Gemini CLI reads it when you start gemini at the repository root, in a folder you trust.
Content stays with you
Prompts, outputs, commands and file contents are committed as salted hashes before anything leaves your machine.
The Gemini CLI hooks Euthyne uses
Sessions
SessionStart and SessionEnd open and close the record of each session.
Prompts
BeforeAgent records each prompt, with its text kept as a salted hash.
Policy decisions
BeforeTool checks each tool call against your org's signed policy, when it has one, and signs the decision. An ask rule denies.
Tool calls
AfterTool records shell commands, file writes and edits, reads, web searches and MCP calls, with their outcome and the files they touch.
Turns
AfterAgent records the end of each turn, with the tokens it used.
From install to the first Gemini CLI 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 gemini-cli
Read the consent text, sign in through your browser and enrol the repository. Init writes the Gemini CLI hooks. Nothing is recorded before you accept.
Start gemini in the repository
Start gemini at the repository root and trust the folder when it asks. Gemini CLI warns once that it found the Euthyne hooks, then runs them.
curl -fsSL https://euthyne.com/install | shbrew install euthyne-labs/tap/euthyneeuthyne init --agent gemini-cliCommon questions
Yes. Euthyne records Gemini CLI today, in the repositories you enrol.
Six: SessionStart, BeforeAgent, BeforeTool, AfterTool, AfterAgent and SessionEnd. Each runs euthyne hook gemini-cli, and BeforeTool runs euthyne hook gemini-cli BeforeTool. They print nothing unless your org enforces a policy that denies a tool call.
No. Euthyne reads tokens from the Gemini CLI session file on your machine, and Gemini CLI does not report cost there, so Gemini CLI receipts carry tokens without a cost.
Euthyne records agents, not model providers. When an agent Euthyne records calls a Gemini model, each receipt names that model.
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 Gemini CLI's BeforeTool deny, and Gemini 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. web_fetch takes a free-text prompt, so only a deny rule can decide it; otherwise it follows your org's setting for actions it cannot evaluate. Gemini CLI 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 Gemini CLI checked 23 Oct 2026 against its documentation. Spot something out of date? Write to hello@euthyne.com.
Gemini is a trademark of Google LLC. Euthyne is not affiliated with, endorsed by or sponsored by Google.
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