Tracekit
Tracekit's signer decides every tool call before it runs (deny blocks, ask waits for a person) and signs each call and its outcome into a run you can verify offline.
Good to know before installing
Every tool call's name and arguments, plus its result (in full for tools Tracekit's policy marks untrusted, otherwise a SHA-256 digest), go to a Tracekit signer: by default a same-user dev signer (`python -m tracekit signer serve --dev`) that the plugin starts on first use as a detached background process, which keeps running after Hermes exits until 15 minutes idle and stores signed runs plus each call's redacted arguments and results (encrypted, kept 7 days) under your user's data directory (~/.local/share/tracekit on Linux), or a remote signer when you set TRACEKIT_SIGNER to an https:// URL. The plugin fails closed: when tracekit-ai can't load or the signer refuses or can't be reached, tool calls are blocked (including every tool an execute_code script calls), and an `ask` decision holds the call until someone approves it in Tracekit or Hermes's hook timeout runs out.
From the plugin's catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs (this one needs
TRACEKIT_SIGNER_TOKEN), then asks whether to turn it on.hermes plugins install tracekit - Said no? Turn it on later:
hermes plugins enable tracekit - 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
- Coding & developer tools
- Maintained by
- Cygnux-Labs (Community)
- Needs
TRACEKIT_SIGNER_TOKENAPI key- Needs Hermes
- 0.22.5 or newer
- Version
- 0.1.0
- In the catalog
- 2026-10-27
- GitHub stars
- 259
Full setup & settings ↗Source code ↗
More in coding & developer tools
All coding & developer tools plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher