Know what a coding agent ran
When an agent runs a command, edits a file or fetches a page, Euthyne records it in a signed receipt with the permission rule that applied. Incident review starts from evidence, not memory.
Who, what, and under which rules
Which agent, which human
Each receipt names the Euthyne user, the device, the harness, the model and the session.
What it ran
Tool, outcome and file paths in clear. The command itself is a salted hash the developer can reveal, one field at a time.
Inside the rules or not
Each action is checked against the signed mandate: in, out or unknown, with the rule and the reason.
Records that do not depend on trust
Signed at the source
Receipts are signed on the developer's machine, by a session key the device key certifies.
Logged
The transparency log proves inclusion and consistency. A forked or rolled back log stops sync.
Anchored
Checkpoints are anchored on chain, so history cannot be rewritten quietly.
Where to go next
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