← Back to overview
Optional feature

Reaching for a cloud model? Filter secrets out first.

Redaction keeps you sovereign over your own data by reducing what's transmitted to the model. It's an optional per-thread setting you enable from the plugin — most useful when you do use a cloud provider.

How it works

With it on, it runs at the gateway, on your machine, on the path out: it targets the read_file and terminal tools specifically, because those are what surface real file contents and command output into the transcript — the egress points where your data would otherwise leave your machine.

That output is scanned and rewritten before it's streamed to the agent or sent to any provider, so the model reasons over <<REDACTED_*>> placeholders for the values it detects. It filters detected secrets in that output — it does not cover text you type or paste into the chat yourself.

A live IDEAgent turn: terminal and read_file tool output with secret values shown as redacted secret tokens, and a note that the agent must not write those redacted tokens back
  • Egress-side, not trust-side
    When enabled, detected secrets are replaced with placeholders before that output leaves the gateway — rather than relying on the provider to discard them afterwards.
  • Targeted detection
    IPs, emails, API keys, tokens are detected and replaced with distinctive tokens like <<REDACTED_IP_ADDRESS>>.
  • Enforced by the agent
    IDEAgent will not write a redacted token back into a file verbatim, so a redacted value can't silently re-enter your codebase through an edit.