checks if they're actually done.A receipt for every claim: what was verified, and what is still open.
Copies a prompt. Paste it into your agent: it installs Yoetz and shows you every change first.Copies a prompt. Stable on macOS; Linux and Windows (via WSL 2) experimental.
Stable on macOS. Linux and Windows (via WSL 2) are experimental.
By keeping two records: what the agent says it did, and what it actually did.
A disagreement is a finding. The agent fixes it, rechecks, and you get a receipt.
The agent talks to Yoetz over MCP. The host reports through hooks. One service on your machine holds the record and checks it.Two records in, one receipt out. One service on your machine.
The agent publishes its plan, work, claims, and evidence through six tools. Any MCP host can, with nothing installed.The agent publishes its plan, work, claims, and evidence.
Codex, Claude Code, and Cursor also report what actually happened: sessions, tool calls, edits. Structural facts, never your files.The host reports what actually happened. Never your files.
Both records land in an append-only ledger. Local rules compare them, and the receipt states exactly how far the check reached.Rules compare the two records. The receipt says how far the check reached.
Yoetz is fresh. It works today with no account and no network, and every claim on this page is tracked in the repository. Expect edges; tell us where they are.