<!-- Emet · /integrations/claude-code · machine-readable copy of https://emet.so/integrations/claude-code -->

> Claude Code plugin for Emet: each turn is sent in the background, and the claims in Claude's answer are checked against the tool results behind them.

_CLAUDE CODE + EMET_

# 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.

_In Claude Code_
```text
/plugin marketplace add FUSEis/emet-plugin
/plugin install emet@emet-plugin
/plugin configure emet@emet-plugin
```

[View on GitHub →](https://github.com/FUSEis/emet-plugin)

[Book a Demo →](https://emet.so/contact)

_HOW IT WORKS_

## Nothing changes in how you work.

- **01 · 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.
- **02 · The whole turn.** — Your prompt, every model call, every tool call with its arguments and result, and every subagent the turn launched.
- **03 · 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.

_WHAT COMES BACK_

## 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.

_Claude Code · 1 turn · 7 tool calls · 3 claims · 1 corrected · 1 flagged_

**acme-api · fix/refund-rounding**

- **VERIFIED** — `round_currency()` is called in three places, all in `billing/`.
  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._

_INSTALL_

## Set up in three steps.

- **01 · Install the plugin.** — Run the three commands above in Claude Code.
- **02 · Enter your key and Team ID.** — From Emet. The key is kept in Claude Code's secure credential store, never in the conversation.
- **03 · 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.

_Setup prompt_
```text
Install the Emet plugin for Claude Code from https://github.com/FUSEis/emet-plugin
and walk me through connecting it.

What it needs:
- Team ID (required): the External ID of my team in Emet, under Teams in the sidebar.
- Emet key (required, secret): my team's key, from Applications, then Manage keys,
  in Emet. I type it in myself.
- My Emet email (optional): only if I don't sign in to Claude with the email of my
  Emet account, or I use Claude through an API key, Bedrock, Vertex AI or a gateway.
- Capture mode (optional): keep the default, `sanitized`, unless I ask.

Rules: never ask me for the key, and never read, print or store it. Do not edit
settings.json files.

1. Run `claude plugin list`. If `emet@emet-plugin` is installed, note its
   version, run `claude plugin marketplace update emet-plugin` and
   `claude plugin update emet@emet-plugin`. If it was older than 0.1.3, skip
   to step 4 (the key has to be entered again). Otherwise skip to the last
   two bullets of step 4.
2. Run `claude auth status --text`. If I'm signed in with a Claude account, show
   me its email and ask whether it is the email of my Emet account. If it is not,
   or I'm not signed in with a Claude account, ask me for my Emet email.
3. Ask me for my Team ID, then run:
   - `claude plugin marketplace add FUSEis/emet-plugin`
   - `claude plugin install emet@emet-plugin --config tenant_ref=<Team ID>`,
     adding `--config emet_email=<email>` if I gave one (only a plain address:
     letters, digits, `.` `_` `%` `+` `-` and one `@`; otherwise I run it myself).
   It reports options that are not set yet. That is expected: the key is left.
4. Tell me, in one short list, to:
   - run `/plugin configure emet@emet-plugin`, type the key into the Emet key
     field and choose Save configuration;
   - restart Claude Code (this conversation ends there);
   - in the new session, run `/emet:setup`, which checks the key and, after my
     first turn, links its report in Emet.
```

[The prompt on GitHub →](https://github.com/FUSEis/emet-plugin#install-with-your-agent)

_FOR THE WHOLE TEAM_

## 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.

[Read the rollout guide →](https://github.com/FUSEis/emet-plugin/blob/main/docs/enterprise.md)

_WHAT IS SENT_

## You choose how much leaves the machine.

| Capture mode | What is sent | Use when |
| --- | --- | --- |
| `sanitized` (default) | The whole turn, with known formats of API keys, tokens, passwords and private keys redacted first. | Developers work with ordinary code and data. |
| `full` | The whole turn as is, except Emet keys. | Sessions cannot contain secrets, such as sandboxes. |
| `metadata` | Models, token counts, timings, tool names, the repository folder name and git branch, and the developer's email. No content, so Emet cannot check claims. | Content must never leave the machine. |

_Sent only to Emet, over HTTPS. Images never leave the machine. The hook is open source, in Python's standard library._

[See exactly what each mode sends →](https://github.com/FUSEis/emet-plugin/blob/main/claude/README.md#what-is-sent)

---

## Stop babysitting AI. Start trusting it.

Emet delivers deterministic verification for enterprise AI data analysis — in seconds, with a receipt.

**[Book a Demo →](https://emet.so/contact)**

---

Emet · Truth infrastructure for AI data systems · https://emet.so
