Redact offline
The model comes with the CLI and runs on your CPU.
How detection worksBefore you send logs or text to an AI provider, run them through redakt. Its built-in model masks detected email addresses and labeled passwords offline. Review the redacted copy before you send it.
Email: ops@example.test
Level: warning
Password: demo-password redakt < support.logEmail: [EMAIL_1]
Level: warning
Password: [SECRET_1]OpenRouter warned that a third party may have read some requests sent to MiniMax after unique test links in those prompts were opened days later. Read the Privacy Affairs report.
Run redakt with a new output path to keep the original intact. Check the copy for secrets or private details the model missed, then paste only what the AI needs.
redakt < support.log > support.redacted.log
The model comes with the CLI and runs on your CPU.
How detection worksThe same email address gets the same label throughout a document.
See what redakt detectsStream JSONL and get the original start and end of each match.
Read the JSONL guideHave Cargo? Copy the command and run it in your terminal.
Browse GitHub releasesTo redact names in English prose, install the development build.
cargo install redakt --lockedPaste the setup prompt from your project folder to add local redaction to its instructions.
Check whether redakt is on PATH. If it’s missing and Cargo is available, install it with `cargo install redakt --locked`. Add the rule below to this project’s assistant instructions. Use AGENTS.md for Codex or CLAUDE.md for Claude Code. Keep the existing instructions. When I ask you to share or analyze a potentially sensitive log or text file, pass it to redakt through stdin before opening it. Save stdout to a new local file that only my account can access. Leave the original untouched. Keep both files’ contents out of chat, tool output, and external services. Give me the redacted file path so I can review the copy before sharing. Verify the setup with a synthetic email address. Tell me which instruction file you updated and whether the test passed.
Run redakt locally on support.log and save the result as support.redacted.log. Pass the source file to redakt through stdin before opening it. Save stdout to a new local file that only my account can access. Leave the source unchanged. Keep file contents out of chat, tool output, and external services. Report only the output path so I can review it locally. If the command fails, summarize the error without quoting file contents.
Run redakt --jsonl locally on events.jsonl and save the result as events.redacted.jsonl. Each input line must contain an id and text. Pass the source file to redakt through stdin before opening it. Save stdout to a new local file that only my account can access. Leave the source unchanged. Keep file contents out of chat, tool output, and external services. Report only the output path so I can review it locally. If the command fails, summarize the error without quoting file contents.