Muse Code audit trail, planned
Muse Code is Meta's coding agent for the terminal and CI, run with the muse command on Muse models. Euthyne does not record Muse Code yet. Support is planned.
Nothing yet. Here is the plan for Muse Code
Prompts and tool callsPlanned
Each prompt, tool call and session event becomes a receipt signed on your machine. Content stays with you as salted hashes.
MandatesPlanned
The permission rules each action ran under are signed as a mandate, and each action is checked against them.
Tokens and costPlanned
Tokens and cost for each session, read from the agent's own usage data on your machine.
User-level installPlanned
Hooks in your user settings run in every project. Only the repositories you enrol are recorded.
Repo-level installPlanned
Hooks in the repository's own settings, kept out of git, for that repository only.
Content stays with youPlanned
Prompts, outputs, commands and file contents are committed as salted hashes before anything leaves your machine.
Muse Code support is planned. Until it ships, Euthyne records nothing for Muse Code.
How Euthyne would plug into Muse Code
Muse Code binds shell commands to 17 lifecycle events, such as SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PermissionRequest, SubagentStart, Stop and SessionEnd. Hooks live in the hooks block of ~/.config/muse/settings.json or in .muse/hooks.json in a project you trusted. Its docs do not yet say how a hook receives the event.
dev.meta.aichecked 18 Oct 2026
Get told when Muse Code ships
Leave your work email and we'll write once, when Euthyne records Muse Code.
Common questions
Not yet. Muse Code support is planned, with no date. Nothing is recorded for Muse Code until it ships.
The shape of the event each hook receives. Muse Code documents its hook events but not yet their payload, and receipts are built from that payload.
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 Muse Code checked 18 Oct 2026 against its documentation. Spot something out of date? Write to hello@euthyne.com.
Meta and Muse are trademarks of Meta Platforms, Inc. Euthyne is not affiliated with, endorsed by or sponsored by Meta.