An audit trail for OpenCode
Euthyne plugs into OpenCode through a small plugin that hands each event to the Euthyne CLI. Every prompt, tool call and permission request in an enrolled repository becomes a signed receipt, in the same format as Claude Code and Codex.
What Euthyne records for OpenCode
Prompts and tool calls
Prompts, bash commands, edits, writes and patches with every file they touch, web fetches, MCP calls, permission requests and replies, and turn ends become signed receipts. Content stays on your machine as salted hashes.
MandatesPartial
The permission rules and MCP server names in your opencode.json files are signed in the mandate as text. They are not evaluated yet, so checks read unknown. Euthyne records, it never blocks a tool call.
Tokens and cost
Tokens in and out, cache reads and writes, and cost for each turn, as OpenCode reports them for the session.
User-level install
--hooks user writes the plugin to ~/.config/opencode/plugins/euthyne.js so it runs in every project.
Repo-level install
--hooks repo writes the plugin to .opencode/plugins/euthyne.js in the repository and keeps it out of git.
Content stays with you
Prompts, outputs, commands and file contents are committed as salted hashes before anything leaves your machine.
The OpenCode hooks Euthyne uses
Sessions
session.created and session.deleted open and close the record of each session.
Prompts
chat.message records each prompt, with its text kept as a salted hash.
Tool calls
tool.execute.after records bash, edits, writes, patches, web fetches and MCP calls, with the files they touch.
Permissions
permission.asked and permission.replied record each time OpenCode asks, and whether you allowed or rejected it.
Turns
session.idle and session.error record the end of each turn, with the tokens and cost it used.
From install to the first OpenCode 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 opencode
Read the consent text, sign in through your browser and enrol the repository. Init writes the Euthyne plugin. Nothing is recorded before you accept.
Restart OpenCode
OpenCode loads plugins when it starts. Restart any OpenCode already running and the next session is recorded.
curl -fsSL https://euthyne.com/install | shbrew install euthyne-labs/tap/euthyneeuthyne init --agent opencodeCommon questions
Yes. Euthyne records OpenCode today, in the repositories you enrol.
It is one short JavaScript file with no dependencies. On each event it runs euthyne hook opencode and passes the event as JSON on stdin. The CLI signs the receipt, the plugin never touches the network.
No. OpenCode is record only, even when your org enforces a policy. Euthyne records what OpenCode does and the permission rules in force. Allowing, asking and denying stays with OpenCode's own permission config.
Yes. OpenCode reports tokens and cost for each session, and Euthyne signs them with the turn that used them.
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 OpenCode checked 19 Oct 2026 against its documentation. Spot something out of date? Write to hello@euthyne.com.
OpenCode is a trademark of its owner. Euthyne is not affiliated with, endorsed by or sponsored by Anomaly.
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