Sealed
From its catalog listing
Secret source that keeps provider credentials in one AES-256-GCM encrypted file instead of plaintext .env: a 32-byte key file unlocks the store at startup and the Hermes secret orchestrator applies the values, so precedence and provenance behave like any other source. Ships `hermes sealed init/set/unset/list/status/rotate`; values are read from a prompt or stdin and are never printed or passed in argv.
Good to know before installing
no network, no helper CLI, no subprocesses. Reads the configured store and key file only (default $HERMES_HOME/secrets/sealed.{store,key}, both 0600); refuses to load when a file is group/world readable if secrets.sealed.strict_permissions is on. The CLI writes those two paths (plus .bak copies on init --force and rotate); values are entered by prompt or stdin. By default sealed values overwrite .env / shell values for the same variable (secrets.sealed.override_existing). No telemetry, no self-updater, no daemon. Requires the `cryptography` package, declared as a plugin dependency.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install sealed - Said no? Turn it on later:
hermes plugins enable sealed - 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
- kailashrajh (Community)
- Needs
- No API keys declared
- Works on
- linux, macos, windows
- Needs Hermes
- 0.22.0 or newer
- Version
- 1.0.0
- In the catalog
- 2026-11-09
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in security & privacy
All security & privacy plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher