What it does
Redacts caller-supplied literal words or strings (a name, a project codename, a reference number) from a Kiteworks folder — previews per-file match counts, and on confirmation writes a redacted copy next to each file and quarantines the original for human deletion. The terms you type are never echoed back in any report.
See it in action
Redact "Project Falcon" from Legal/Contracts and show me what would change
Pinning Legal/Contracts and counting how many times "Project Falcon" occurs in every supported file. You get per-file MATCH COUNTS only — the term and the matched text never leave the platform, and nothing is changed in a preview.
| File | Matches |
|---|---|
| msa-2026.docx | 5 |
| board-notes.txt | 4 |
| nda-draft.docx | 2 |
Redact the files we just previewed in Legal/Contracts
Re-checking the folder against the confirmed plan first — if anything changed since the preview, the apply refuses and nothing is touched. Then each planned file gets a redacted copy, and the original moves to "To delete".
| Original | Redacted copy | Original moved to |
|---|---|---|
| board-notes.txt | board-notes-redacted.txt | To delete |
| msa-2026.docx | msa-2026-redacted.docx | To delete |
| nda-draft.docx | nda-draft-redacted.docx | To delete |
Relevant regulations and standards
Frameworks and mandates this agent helps you address. Not a certification — your own controls and assessment still apply.
Tags
What's new
latest 0.2.0Published version history. The latest version is what new installs receive; your administrator chooses when to upgrade.
-
0.2.0stable breaking latest 2026-06-15Confirmation key source change (ADR 0006, supersedes 0005). The preview→apply confirmation token is UNCHANGED — still a context-bound, platform-keyed HMAC that binds the term set (so a same-count term swap is refused) and is not a dictionary oracle. What changed: the MAC key is now HKDF-derived (domain-separated) from the existing mandatory
KW_SESSION_SECRETinstead of a dedicatedKW_LITERAL_CONFIRM_KEY. This removes the separate-secret provisioning footgun — the redactor activates wherever the[entities]engine and the platform session secret are present (the latter is already required in OIDC/production). No input/output schema change and no change to term confidentiality or per-file redaction behaviour; minor bump because the token VALUE no longer validates across the key-source change (re-run preview). -
0.1.0stable 2026-06-15Initial literal-term redaction agent (LITERAL-TERM-REDACTION-PLAN Phase 1). Preview → confirm → apply over a platform-keyed, context-bound
confirmation_token(§5.7; key policy ADR 0005). Redacts caller-supplied literal strings via theliteral-redactioncapability and the platform content lane; the terms never appear in any output. Text + Office (mask/replace where applicable) and image/PDF (mask, OCR) supported; low-confidence pages are blocked, never treated as clean. Ships English-only; nl/he/ja overlays are a reviewed fast-follow.
Install in Claude Code
claude plugin marketplace add \
kiteworks/agent-marketplace
claude plugin install \
kiteworks-redactor@kiteworks
Prerequisites
-
Kiteworks Compliance Runtime — install via
pip install kw-mcp-gateway(host>=1.0.0,<2.0.0). This agent calls into the runtime for deterministic, audited execution. -
Official Kiteworks MCP
>=9.3.0(used by the runtime) — install and sign in from github.com/kiteworks/mcp. - Python
>=3.11.
Connect from Claude
Add this marketplace as a remote MCP connector in Claude Desktop or Claude Code — point it at <your-host>/mcp. One process per deployment; no per-machine install. Requires the official Kiteworks MCP to be configured.