An audit trail for Antigravity CLI
Euthyne plugs into Google Antigravity through its command hooks. Every shell command, file edit and tool call in an enrolled repository becomes a signed receipt, in the same format as Claude Code. The same hooks run in the Antigravity CLI, app and IDE.
What Euthyne records for Antigravity CLI
Prompts and tool calls
Session starts, tool calls (run_command, file writes and edits with the files they touch, reads, searches, MCP and subagent calls) and turn ends become signed receipts. Antigravity hooks carry no prompt and no session end, so neither is recorded. Content stays on your machine as salted hashes.
MandatesPartial
Your toolPermission setting and the allow, ask and deny rules in the Antigravity settings.json are signed into the mandate as text. They are not evaluated yet, so checks read unknown.
Tokens and costPartial
Tokens in and out, read from the Antigravity transcript on your machine. Antigravity reports no cost, so receipts carry none.
User-level install
--hooks user adds a euthyne entry to ~/.gemini/config/hooks.json so the hooks run in every project. Gemini CLI's ~/.gemini/settings.json is never touched.
Repo-level install
--hooks repo writes .agents/hooks.json in the repository and git-ignores it.
Content stays with you
Prompts, outputs, commands and file contents are committed as salted hashes before anything leaves your machine.
The Antigravity CLI hooks Euthyne uses
Sessions
SessionStart opens the record of each conversation.
Tool calls
PostToolUse records run_command, file writes and edits, reads, searches and MCP calls, with their outcome and the files they touch.
Turns
Stop records the end of each turn and why it ended.
From install to the first Antigravity 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 antigravity
Read the consent text, sign in through your browser and enrol the repository. Init writes the Antigravity hooks. Nothing is recorded before you accept.
Run agy
Start agy in the repository. The hooks run from the next session, and /hooks lists them.
curl -fsSL https://euthyne.com/install | shbrew install euthyne-labs/tap/euthyneeuthyne init --agent antigravityCommon questions
Yes. Euthyne records Antigravity CLI today, in the repositories you enrol.
Three, under a hook named euthyne: SessionStart, PostToolUse and Stop. Each runs euthyne hook antigravity with the event name. Euthyne never installs PreToolUse, so it cannot block a tool call.
Yes. Antigravity runs the same hooks.json in its app, IDE and CLI, so the hooks record all three. The mandate reads the settings.json of whichever one ran the session, when it has one.
No. Euthyne reads tokens from the Antigravity transcript on your machine, and Antigravity does not report cost there, so receipts carry tokens without a cost.
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 Antigravity CLI checked 19 Oct 2026 against its documentation. Spot something out of date? Write to hello@euthyne.com.
Google and Antigravity are trademarks 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