An audit trail for Cursor
Euthyne plugs into Cursor through its own hooks, in the editor's agent and in the cursor-agent CLI. Every prompt, shell command, file edit and MCP call in an enrolled repository becomes a signed receipt, in the same format as Claude Code.
What Euthyne records for Cursor
Prompts and tool calls
Prompts, shell commands, file reads and edits with the files they touch, MCP calls, tool failures, subagents and turns become signed receipts. Tab completions are not recorded. Content stays on your machine as salted hashes.
MandatesPartial
The cursor-agent CLI allow and deny lists and your MCP server names are signed as a mandate, kept as text and not evaluated yet, so checks read unknown. The editor keeps its auto-run settings outside these files. On Team and Company, your org's signed policy decides each tool call in the editor's agent before it runs, offline. Enforced, fails open on timeout: Cursor runs the call if the hook times out or is killed. Euthyne leaves out failClosed because Cursor then needs an explicit allow from the hook, and Euthyne never answers allow. The cursor-agent CLI does not fire preToolUse yet, so there it is recorded but not blocked.
Tokens and costNo
Cursor's hooks pass no token counts or cost, so Cursor receipts carry none.
User-level install
--hooks user writes ~/.cursor/hooks.json, with a backup, so the hooks run in every project. Only enrolled repositories are recorded.
Repo-level install
--hooks repo writes .cursor/hooks.json in the repository and keeps it out of git. Cursor runs project hooks once you trust the workspace.
Content stays with you
Prompts, outputs, commands and file contents are committed as salted hashes before anything leaves your machine.
The Cursor hooks Euthyne uses
Sessions
sessionStart and sessionEnd open and close the record of each conversation.
Prompts
beforeSubmitPrompt records each prompt and its attachments, kept as salted hashes.
Policy decisions
preToolUse checks each tool call against your org's signed policy, when it has one, and signs the decision. Cursor cannot ask from preToolUse, so an ask rule denies.
Tool calls
postToolUse and postToolUseFailure record shell commands, file reads and edits, MCP calls, their outcome, duration and the files they touch.
Subagents
subagentStop records each subagent when it ends, with the files it modified.
Turns
stop records the end of each agent turn, whether it completed, was aborted or failed.
From install to the first Cursor 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 cursor
Read the consent text, sign in through your browser and enrol the repository. Init writes the Cursor hooks. Nothing is recorded before you accept.
Trust the workspace
Cursor runs project hooks only in a trusted workspace. Open the repository in Cursor and trust it, or pass --trust to cursor-agent in a headless run.
curl -fsSL https://euthyne.com/install | shbrew install euthyne-labs/tap/euthyneeuthyne init --agent cursorCommon questions
Yes. Euthyne records Cursor today, in the repositories you enrol.
Yes. The editor's agent and the cursor-agent CLI read the same hooks.json files, so one euthyne init --agent cursor covers both.
Eight: sessionStart, beforeSubmitPrompt, preToolUse, postToolUse, postToolUseFailure, subagentStop, stop and sessionEnd. Each runs euthyne hook cursor, and preToolUse runs euthyne hook cursor preToolUse. preToolUse only decides when your org has an enforced policy; otherwise it prints nothing.
No. Cursor also runs the hooks in your Claude Code settings, but the Claude Code hook recognises Cursor's events and skips them, so the Cursor hooks record each action once.
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 Cursor's preToolUse permission, and the agent 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. Cursor runs the call anyway if the hook times out, so we label it enforced, fails open on timeout. Cursor's preToolUse does not name the MCP server, so every Cursor MCP call is denied while a policy is enforced. The cursor-agent CLI does not run preToolUse yet, so it is recorded only.
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 Cursor checked 23 Oct 2026 against its documentation. Spot something out of date? Write to hello@euthyne.com.
Cursor is a trademark of Anysphere, Inc. Euthyne is not affiliated with, endorsed by or sponsored by Anysphere.
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