Secret Remediation

From its catalog listing

Fingerprint leaked credentials in the Hermes workspace, logs, and session history. Redacts them, blocks the turn, and gives text-only rotation advice.

Good to know before installing

Rewrites credential matches into fingerprint placeholders in tool results, terminal output and replies, blocks turns or tool calls that contain credential-shaped text, and keeps fingerprint-only incident records under its plugin-data directory; it reads state.db and spawn-ledger.json read-only to report affected session ids, and only `hermes secret-remediation purge --shell-history` (operator CLI) rewrites your bash/zsh/fish history files after a safety copy; an operator-run `hermes secret-remediation schedule` adds a no-agent Hermes cron scan; no network calls.

From its catalog listing.

How to install

  1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
    hermes plugins install secret-remediation
  2. Said no? Turn it on later:
    hermes plugins enable secret-remediation
  3. Restart Hermes so it loads the plugin.

Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).

Category
Security & privacy
Maintained by
AdrianTanz (Community)
Needs
No API keys declared
Adds hooks
pre_llm_call pre_tool_call transform_tool_result transform_terminal_output transform_llm_output
Needs Hermes
0.23.0 or newer
Version
0.1.0
In the catalog
2026-11-11

Known issues (from its catalog listing)

  • After a block, the plugin tries to replace credential text in state.db messages.display_metadata.withheld_prompt, state.db session_admissions.payload_json, and spawn-ledger.json argv with a fingerprint placeholder. payload_digest is recomputed, so replaying the original request is refused. That is expected. A failed attempt is logged and the plaintext can remain. Hermes can write the value again after the short retry window.
  • Purge writes by default, including shell history outside Hermes and chat history. Opt out with --no-sessions, --no-messages, --no-shell-history, --no-backups, --no-vacuum, including on scan --purge. A blocked-turn /retry reads withheld_prompt. The content, api_content, tool_calls, and display_metadata rewrite is separate, so a replayed tool call sends the placeholder. payload_digest is recomputed and an original replay is refused. VACUUM is skipped and named incomplete when state.db or its WAL is open. backups/pre-update-*.zip and backups/pre-migration-*.zip are counted and not rewritten. Provider logs, Time Machine, and cloud sync are not cleared. Close other shells first, or run history -c, or a running shell can write history back on exit. History mtime is kept.
  • Detects known token prefixes, PEM blocks including a BEGIN line with no END, equals-assignments named password, api_key, or secret (8 or more characters), URL userinfo for a fixed scheme list, and Authorization Bearer tokens. Unlabelled AWS secrets are detected only when the 40-character token contains + or / and is not hex, and that shape is not registered with Hermes's redactor. Encoded, split, Authorization Basic, colon assignments, and all-hex 40-character strings can pass.
  • The scheduled scan prints only new fingerprints. A clean tick is silent.
Using the Hermes desktop app? See where plugins live
Hermes desktop Capabilities page, Plugins tab filtered to Official plugins built by Nous Research, each with an add button.
The official plugin catalog built into the app.Hermes desktop v0.22.5 · Capabilities > Plugins · Windows · captured Nov 1, 2026

Full setup & settings ↗Source code ↗

More in security & privacy

All security & privacy plugins

New Hermes Agent updates every day on X. Follow @HermesWatcher

← All plugins