Check what Claude Code tells you.
The Emet plugin sends each Claude Code turn to Emet after it ends. Emet checks the claims in Claude's answer against the tool results, files and data Claude actually received.
Nothing changes in how you work.
Each turn, after it ends.
Claude Code's hooks hand the finished turn to the plugin, which sends it in the background. Claude never waits on Emet.
The whole turn.
Your prompt, every model call, every tool call with its arguments and result, and every subagent the turn launched.
Checked against the evidence.
Emet compares each claim in Claude's answer with what the tools returned, and /emet:status links the turn's report in Emet.
A verdict on every claim.
Each finished turn becomes a report in Emet: every claim in Claude's answer, its verdict, and the tool result behind it.
SAMPLE REPORT · ILLUSTRATIVE DATA
acme-api · fix/refund-rounding
Claude Code · 1 turn · 7 tool calls · 3 claims · 1 corrected · 1 flagged
- VERIFIED
round_currency()is called in three places, all inbilling/.src: Grep · 3 matches, all in billing/ · exact match
- CORRECTED
All 214 213 of 214 tests pass.
src: Bash · pytest · 213 passed, 1 failed
The last pytest run in the turn returned 213 passed, 1 failed: test_partial_refund. Corrected from that tool result.
- FLAGGED
Totals on invoices already issued don't change.
src: none · no tool result to check against
No tool call in the turn read or tested issued invoices, so nothing confirms or contradicts this. Emet flags it rather than guess.
SAMPLE REPORT · ILLUSTRATIVE DATA · Acme is a fictional company; the turn is illustrative.
Set up in three steps.
Install the plugin.
Run the three commands above in Claude Code.
Enter your key and Team ID.
From Emet. The key is kept in Claude Code's secure credential store, never in the conversation.
Restart and check.
Restart Claude Code, then run /emet:setup. After your first turn it links the turn's report in Emet.
Or let Claude set it up.
Paste this prompt into Claude Code. Claude installs the plugin, asks for your Team ID, and has you type the key into Claude Code's own dialog, so the key never enters the conversation.
Roll it out to every developer at once.
An administrator installs and configures the plugin for everyone through Claude Code's managed settings. Developers enter nothing — except their email, if they don't sign in to Claude.
Configured centrally.
The team's key, Team ID and capture mode come from managed settings. Developers cannot change the team or the capture mode, or turn the plugin off.
Attributed to each developer.
Each turn carries the email the developer signs in to Claude with, so Emet shows who ran it.
Released on your schedule.
Pin a release, and a new version reaches developers only when you move the pin.
You choose how much leaves the machine.
sanitized (default)fullmetadataSent only to Emet, over HTTPS. Images never leave the machine. The hook is open source, in Python's standard library.