Tenure
From its catalog listing
Revocable trust for Hermes agents, per action type. By default every kind of action works as with Hermes alone (files, memory, subagents, known dev tools: npm, pytest, cargo, git...), and every local change is saved first: file writes and plain rm, mv, cp, sed -i or `> file` on project files act, then tell you, with `/tenure undo` for 24 hours. The first mistake on a kind of action (an undo, a flag, a refusal of Hermes's own prompt, a file it wrote that no longer parses) puts that kind, for every model of the profile, on probation: it asks first, earns back acting-then-notifying on a run of approvals, then acting alone with random spot checks, from a rule preregistered on OSF (Wald SPRT to the middle tier, Dodge's CSP-1 series to the top, a guarantee you choose). What leaves the machine (push, publish, deploy, registry logins, cloud writes, payments), unreadable shell, and anything after the agent read outside content keep asking; one "Allow for this session" covers a session. Signed, hash-chained, replayable autonomy passport (`hermes tenure verify`), a per-model benchmark of your own work, a switch preview before you change model, a Desktop page and a dashboard tab at parity, five languages. Linux, macOS and Windows (on Windows, plain shell file commands keep asking instead of acting with an undo). A friction bench in the repo replays an ordinary 30-call coding session: 3 questions Hermes would not ask, against 23 when every kind of action asks first.
Good to know before installing
hooks only (pre_api_request, pre_tool_call, post_approval_response, post_tool_call, post_llm_call, subagent_start, subagent_stop), no tools; no network, no LLM call, runs no command. It can only add an approval prompt through Hermes' own prompt, never answer one. Reads the profile's config.yaml and its own plugin settings, and writes settings back only through ctx.set_config when the owner saves them. Writes under plugin-data/tenure: a SQLite record and a hash-chained ledger (action types and outcomes, no paths, no commands, no free text), a signing key and an undo HMAC key, and undo snapshots of the project files an action is about to change (file bytes and paths, owner-only, deleted after 24 hours, 5 MB per action). The dashboard tab and Desktop page show the tenure records of every profile on the machine (read-only); revoke, flag, undo and settings act on the current profile only.
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 tenure - Said no? Turn it on later:
hermes plugins enable tenure - 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
- Memory & notes · AI models & providers
- Maintained by
- otsoa-dubief (Community)
- Needs
- No API keys declared
- Adds hooks
pre_api_requestpre_tool_callpost_approval_responsepost_tool_callpost_llm_callsubagent_startsubagent_stop- Needs Hermes
- 0.23.0 or newer
- Version
- 1.0.0
- In the catalog
- 2026-11-14
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in memory & notes
New Hermes Agent updates every day on X. Follow @HermesWatcher