What is Euthyne

Euthyne records what coding agents do in your repositories. Each agent action becomes a signed record, called a receipt. When a pull request merges, Euthyne links it to the agent sessions behind it and to the people who approved it.

Anyone with a receipt can check it. They do not need a Euthyne account, and they do not need to trust Euthyne's servers.

The questions it answersCopy Anchor Link

• Which agent changed this file, and with which model?
• Who launched the agent session?
• Which pull request carried the change, and who approved it?
• Was the approver someone other than the author and the person who launched the agent?

How it worksCopy Anchor Link

1. You run euthyne init in a repository. It signs you in, creates a key for your machine, and installs hooks in your agent harness.
2. Each time the agent uses a tool, the hook signs a receipt on your machine. The receipt holds metadata in clear and the content as salted hashes.
3. The CLI uploads receipts in the background. Euthyne adds each one to an append-only public log.
4. When a pull request merges, Euthyne writes a change receipt. It lists the linked sessions, the approvals and the CI result.
5. Anyone can verify a receipt in the browser, or offline with euthyne verify.

What it supports firstCopy Anchor Link

• Agent harnesses: Claude Code and Codex. Other harnesses are not supported yet.
• Git hosts: GitHub. GitLab support is planned.

What it does not doCopy Anchor Link

• It does not store your prompts, code, diffs or command output. They leave your machine only as salted hashes. See What we store.
• It does not block or approve anything. It records what happened.
• It cannot prove that every agent action was captured. Capture runs through hooks, and a developer can turn hooks off. Euthyne flags merges that have no receipts, but it cannot see agent work that never reached a hook or a pull request.
• A receipt shows that an action was recorded and signed. It does not show that the action was correct or safe.

NextCopy Anchor Link