909 plugins from the official Hermes plugin catalog: 20 official, 9 verified and 880 from the community. 206 were added in the last week. Search, filter by what you want to do, and copy the install command.
118 plugins. Sorted by HermesWatcher's picks: usefulness, polish and trust. Official: made by Nous Research. Verified: listed with a verified maintainer. Community: built by others, so read the source first.
Hindsight
Community
Hindsight long-term memory provider — knowledge graph, entity resolution and multi-strategy retrieval (recall/reflect/retain tools plus automatic per-turn capture).
Hindsight long-term memory provider — knowledge graph, entity resolution and multi-strategy retrieval (recall/reflect/retain tools plus automatic per-turn capture). Maintained by Vectorize; cloud, local external and local embedded modes are available. `hermes memory setup` fetches its bank-template catalog from raw.githubusercontent.com (vectorize-io/hindsight main).
Good to know before installing
In cloud mode (and local external) every turn's conversation, and every entry the agent adds or replaces in Hermes's built-in MEMORY/USER stores, is sent to api.hindsight.vectorize.io or the URL you configure, into every bank it writes to; local embedded mode starts a background Hindsight daemon (fetched with uvx, version-pinned, on first run when hindsight-api is not installed) and keeps its LLM settings in ~/.hindsight/profiles/<profile>.env; setup writes the keys you enter to the profile .env; repositories under folders you list in trusted_project_dirs may choose their bank with .hindsight/config.toml; `hermes memory setup` fetches its bank-template catalog from raw.githubusercontent.com (vectorize-io/hindsight main).
From the plugin's 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 hindsight
Said no? Turn it on later:
hermes plugins enable hindsight
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Hermes Memory Wiki
Official
Memory Wiki dashboard tab and opt-in native Desktop page: browsable subject pages and daily logs derived from local session history, plus a read-only Persistent Memory (MEMORY.md / USER.md) audit panel.
Memory Wiki dashboard tab and opt-in native Desktop page: browsable subject pages and daily logs derived from local session history, plus a read-only Persistent Memory (MEMORY.md / USER.md) audit panel.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-memory-wiki
Said no? Turn it on later:
hermes plugins enable hermes-memory-wiki
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).
Guarded Word, PowerPoint and Excel editing: tracked Word changes and comments, slide and deck edits, and Excel edits with LibreOffice recalc. Every write gets a backup and a revertible receipt, and you review it all on a Desk page in the Desktop app. Settings are in Settings > Plugins.
Good to know before installing
Reads any Office file the agent is pointed at but writes only inside folders the user puts on the Desk (backups and receipts live in the plugin's own data dir). xlsx_recalc runs the user's installed LibreOffice (soffice, headless) on a temporary copy. The Desk page reads the session store read-only to show a workstream's chat. No network calls, telemetry, credentials or background processes. Depends on the paper-docx, paper-pptx and paper-xlsx forks. They provide the docx, pptx and openpyxl import names, so they must not share an environment with python-docx, python-pptx or openpyxl.
From the plugin's 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 office-desk
Said no? Turn it on later:
hermes plugins enable office-desk
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).
Long-term memory for Hermes. Capture conversations, recall useful facts across sessions and search your knowledge. Choose Quick Local, OpenViking Service (managed cloud) or your own server.
Good to know before installing
Conversation turns, tool results and MEMORY.md / USER.md edits are sent to the configured OpenViking server. Quick Local setup installs the newest OpenViking 0.5.x server release from PyPI at setup time (checked against PyPI's hash, not the version reviewed here; re-running setup upgrades it) plus a hash-pinned llama-cpp-python wheel and a local embedding model. It copies the active Hermes static LLM API key into a private file under the profile for extraction, and its localhost server keeps running after Hermes exits and after plugin removal (stop it with `hermes openviking local stop`). Extraction can use a remote LLM. Custom localhost connections can start openviking-server from PATH with the profile environment minus Hermes bot, gateway, GitHub and dashboard secrets; model and tool API keys still pass.
From the plugin's 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 openviking
Said no? Turn it on later:
hermes plugins enable openviking
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Cloud File Manager
Community
Cloud Files for Hermes Desktop — browse, search and sort by date, create folders and bulk-upload files and whole folders to the machine your agent runs on, preview its images, PDFs and code files, download a file, read…
Cloud Files for Hermes Desktop — browse, search and sort by date, create folders and bulk-upload files and whole folders to the machine your agent runs on, preview its images, PDFs and code files, download a file, read and edit its Markdown and text files (view first; nothing is written until you press Save in the review, which shows the line diff for files up to 20,000 lines), drag files into the chat, import files from the agent's own Google Drive, and hand the agent file locations from the chat + menu without re-uploading. Built for remote gateways (token or sign-in); works locally too. Ships one plugin skill, hermes-cloud-file-manager:cloud-file-manager-report-problem, which drafts a bug report and files it with the GitHub CLI only after the user approves the exact text.
Good to know before installing
Adds a file API to the gateway (dashboard plugin routes under the gateway's existing auth) over the agent's working folders: the configured roots, else terminal.cwd, TERMINAL_CWD or MESSAGING_CWD, else the gateway user's home with its dot-entries hidden. It lists, sorts and searches those folders, reads the files you open or preview (Markdown and .txt files up to 1 MiB in the editor; the first 1 MiB of other code and text files; images and PDFs up to 10 MiB), creates folders, and writes uploads, Drive imports and editor saves (staged as hidden .cfm-* temp files in the destination folder; a name clash keeps both files). It overwrites only an existing .md/.markdown/.txt file you open and explicitly Save in its editor (refused if the file changed since you opened it). It has no delete action: it removes only its own .cfm-* staging files and folders (aborted ones, and stale ones over a day old) and, when an upload or import fails to publish, the empty file it had reserved for it. It never follows links out of those folders, and its file API never exposes the agent's Hermes home apart from a working folder set inside it (roots, terminal.cwd, or a workspace/ folder it creates when the wo
From the plugin's 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 hermes-cloud-file-manager
Said no? Turn it on later:
hermes plugins enable hermes-cloud-file-manager
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).
Honcho is memory infrastructure for building stateful agents that understand changing people, agents, groups, projects, and ideas over time. Store messages and events, let Honcho reason in the background, then query peer representations, session context, search results, or natural-language insights from any model or framework. Use it managed at api.honcho.dev, run a local stack with the honcho CLI, or self-host the server yourself. Maintained by Plastic Labs; the same provider that shipped in-tree.
Good to know before installing
Conversation turns, derived conclusions and peer/session ids are sent to the Honcho API (api.honcho.dev by default, or the self-hosted base_url you configure) under your HONCHO_API_KEY; every request also carries X-Honcho-Host (Hermes version and OS platform) and X-Honcho-Plugin (plugin version) headers that Honcho records for usage attribution.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs HONCHO_API_KEY), then asks whether to turn it on.
hermes plugins install honcho
Said no? Turn it on later:
hermes plugins enable honcho
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).
Notes, checklists and documents beside Hermes that your agent can read and update safely, with revision checks and undo for AI edits.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install jot
Said no? Turn it on later:
hermes plugins enable jot
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Mem0
Community
Mem0 memory provider — server-side LLM fact extraction with semantic search, automatic deduplication and opt-in reranking, in platform, self-hosted or local OSS mode.
Mem0 memory provider — server-side LLM fact extraction with semantic search, automatic deduplication and opt-in reranking, in platform, self-hosted or local OSS mode. Maintained by Mem0; the same provider that shipped in-tree.
Good to know before installing
Conversation turns and recall queries go to the configured Mem0 backend (api.mem0.ai in platform mode); at this pin the mem0ai library's anonymous PostHog usage telemetry stays on unless MEM0_TELEMETRY=false is set; `hermes memory setup` can start Docker (pgvector) and Ollama containers for local mode.
From the plugin's 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 mem0
Said no? Turn it on later:
hermes plugins enable mem0
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).
Local Markdown vault workspace for Hermes Desktop: visual editing, progressive reading, cached image previews, optional per-conversation workspaces, pinned tabs, explicit selection quoting, tag search, links, backlinks and a graph. Compatible with Obsidian vaults. File transport requires a Linux/macOS gateway; Windows Desktop requires a WSL-hosted Unix backend, not a native Windows gateway; ffmpeg thumbnails are optional. Remote images and agent guidance are independent opt-ins and disabled by default; automatic note-content sharing is disabled; direct Obsidian opening is temporarily hidden.
Good to know before installing
Reads and writes notes in the vault folder you choose through Desktop shell commands on the gateway host; remote Markdown images and agent navigation guidance stay off until you opt in.
From the plugin's 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 vault-view
Said no? Turn it on later:
hermes plugins enable vault-view
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).
BetterDB long-term memory provider — semantic recall on Valkey / valkey-search via the betterdb-agent-memory SDK. Completed turns are embedded and stored in a vector index; the next turn recalls the most relevant memories with a composite similarity/recency/importance score. Explicit betterdb_remember / betterdb_recall / betterdb_forget tools.
Good to know before installing
Turn text and tool-stored facts are embedded through an OpenAI-compatible embeddings endpoint you configure (embeddings_base_url, default api.openai.com) and written to the Valkey instance you point it at; plaintext http:// to a remote host is refused. Opt-in, off by default: a discovery marker (set discovery=true to let BetterDB Monitor enumerate the tier) and SDK usage analytics (set telemetry=true).
From the plugin's 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 betterdb
Said no? Turn it on later:
hermes plugins enable betterdb
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Tabella
Community
Document lifecycle for agents in one package: create .docx/.xlsx/.pptx/.pdf/.odt/.ods/.odp from structured JSON or raw HTML/CSS, convert between formats via pandoc + LaTeX, and read any document — anydoc (Rust, office…
Document lifecycle for agents in one package: create .docx/.xlsx/.pptx/.pdf/.odt/.ods/.odp from structured JSON or raw HTML/CSS, convert between formats via pandoc + LaTeX, and read any document — anydoc (Rust, office formats and text PDFs to Markdown, in-process) with LiteParse + Tesseract OCR fallback for scanned PDFs and images, plus PDF text editing with output-directory guards. Ships as an Agent Plugins v1 package (auto-discovered plugin.json + mcp.json declaring a stdio MCP server — the client spawns it per the v1 lifecycle, PLUGIN_ROOT/PLUGIN_DATA injected — plus an optional self-host streamable-HTTP server; first run of either bootstraps the dependency venv). The HTTP lane binds to 127.0.0.1 only and requires Bearer auth out of the box: a random token is generated into PLUGIN_DATA on first run (TABELLA_TOKEN overrides); requests with an Origin header or a non-JSON body are rejected, and model-supplied HTML cannot fetch network or local-file resources (data: URIs only — the same fetcher now also guards CSS input, not just HTML). Pandoc invocations are argument-safe: extra_args is allowlisted (--toc, --number-sections, -V key=value) and from_format/to_format are validated against the built-in format-name grammar (^[a-z0-9_]+([+-][a-z0-9_]+)*$), closing pandoc's *.lua reader/writer code-exec path; both servers re-exec into the dependency venv after bootstrap.
Good to know before installing
Python deps (python-docx, openpyxl, python-pptx, weasyprint, odfpy, Pillow, lxml, PyMuPDF, firecrawl-anydoc, liteparse — 10 direct packages, transitives included in a 25-package closure) are pinned to exact versions with sha256 hashes in requirements-pinned.txt and installed with --require-hashes into a venv under PLUGIN_DATA or ~/.venvs/docs (scripts/setup.sh on Linux/macOS; on Windows the venv is built with the standard library's venv module — no bash or MSYS2 needed); system pandoc is required for conversion, a TeX engine (e.g. texlive-xetex) only when the output format is PDF (weasyprint for HTML->PDF); OCR needs the tesseract binary (UB-Mannheim build on Windows); all conversion, reading, OCR and PDF editing run locally with no network or telemetry; nothing is uploaded; read, convert, and PDF-edit tools access exactly the filesystem paths you pass; doc_create_document additionally containment-checks its output paths against the configured output directory (escape warns). Linux and Windows are CI-tested platforms (five-lane smoke battery on windows-latest: stdio lifecycle through a natively bootstrapped venv, create, read, pdf-from-html via the GTK runtime, pandoc convert).
From the plugin's 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 tabella
Said no? Turn it on later:
hermes plugins enable tabella
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).
Memanto memory agent — typed long-term memory (remember/recall/answer) with auto-recall, turn capture, and RAG answers.
Good to know before installing
Each user turn (as a recall query), completed user+assistant turns, Hermes memory writes and memanto_answer questions are sent to Moorcheh cloud (api.moorcheh.ai) under a per-profile agent namespace by default; requires MOORCHEH_API_KEY; settings in $HERMES_HOME/memanto.json.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs MOORCHEH_API_KEY), then asks whether to turn it on.
hermes plugins install memanto
Said no? Turn it on later:
hermes plugins enable memanto
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Stacktree
Community
Publish what Hermes builds (reports, dashboards, briefs, proposals) to a private link that opens in any browser with no account for the viewer, set a passcode or limit it to a company's email addresses, update it in…
Publish what Hermes builds (reports, dashboards, briefs, proposals) to a private link that opens in any browser with no account for the viewer, set a passcode or limit it to a company's email addresses, update it in place, and see who opened it and what they commented. Portable Agent Plugins v1 package (mcp.json + skills/).
Good to know before installing
Hosted-only connector with no local code; every tool call goes to Stacktree's remote MCP server at api.stacktr.ee (OAuth 2.1 with dynamic client registration, token kept by Hermes); the HTML the model passes to publish_html or update_site is stored in the user's Stacktree account and served at the returned link (unlisted by default, public when a public_slug is set); page titles, open counts and third-party reader comments from that account are read into the session; the remote tools that publish, update, gate, delete pages or email approval requests run without a Hermes approval prompt; the required sign-in step `hermes mcp add stacktree --url https://api.stacktr.ee/mcp --auth oauth` writes a config.yaml server entry that replaces the package's own.
From the plugin's 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 stacktree
Said no? Turn it on later:
hermes plugins enable stacktree
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).
Memoria Cloud memory provider with scoped recall, explicit memory tools and opt-in background capture.
Good to know before installing
Sends recall queries and explicit memory operations to api.thememoria.ai by default (or a configured self-hosted origin). When enabled, auto capture uploads completed user/assistant text for fact extraction, excluding tool results and media. A local SQLite outbox stores pending text; credentials are resolved through the active Hermes profile's MEMORIA_API_KEY secret.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs MEMORIA_API_KEY), then asks whether to turn it on.
hermes plugins install memoria
Said no? Turn it on later:
hermes plugins enable memoria
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).
Dual-panel commander file browser for Hermes Desktop — whitelist-guarded file CRUD, copy/move/symlink, media preview, multi-select, rename, and trash. No network I/O, no model tokens.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install filebox
Said no? Turn it on later:
hermes plugins enable filebox
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).
Local-first memory layer for Hermes Agent — SQLite with vector + FTS5 hybrid recall, episodic consolidation, temporal knowledge graph. Zero cloud.
Good to know before installing
The mnemosyne_remember_media tool refuses local file paths unless MNEMOSYNE_MEDIA_ALLOWED_PATHS is set and sends media only to an operator-configured OpenAI-compatible endpoint when modality_enabled is on; video uses ffmpeg/ffprobe from PATH; the embedding model (BAAI/bge-small-en-v1.5) downloads from Hugging Face on first use.
From the plugin's 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 mnemosyne
Said no? Turn it on later:
hermes plugins enable mnemosyne
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).
Browse, search, and edit Obsidian vault notes from the Hermes dashboard. Features force-directed graph visualization, multi-vault support, markdown rendering with wikilinks, and inline note editing.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install obsidian-memory
Said no? Turn it on later:
hermes plugins enable obsidian-memory
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).
Local-first, file-native long-term memory with HTTP and embedded ReMe backends.
Good to know before installing
Search queries and full user/assistant turns are sent to the configured ReMe endpoint (default http://127.0.0.1:2333; a non-loopback http:// endpoint receives them in plaintext) or handled by the in-process ReMe SDK; no API keys are forwarded.
From the plugin's 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 reme
Said no? Turn it on later:
hermes plugins enable reme
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).
Talks to reMarkable cloud with a device token under ~/.hermes/credentials/remarkable/; remarkable_upload sends model-chosen local PDF/EPUB files to your account; the cloud sidecar (Node 22+) and renderer venv are installed only by the human-run setup commands; USB/SSH off by default.
From the plugin's 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 remarkable
Said no? Turn it on later:
hermes plugins enable remarkable
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).
Long-term memory for you and your AI from Membase (membase.com, by Unibase): one memory every connected AI shares. Searches the user's Membase memory before each turn (8 s, fail-open) and adds membase_search, membase_save and membase_profile.
Good to know before installing
User prompts are sent as search queries to the Membase API (api.app.membase.com); with the opt-in capture_turns setting the user's messages are saved there too, and what Hermes' built-in memory records about the user is saved to their Membase profile. MEMBASE_API_KEY comes from the Hermes secret scope; the only local file is $HERMES_HOME/unibaseio-membase.json. No background processes, shell commands or telemetry.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs MEMBASE_API_KEY), then asks whether to turn it on.
hermes plugins install unibaseio-membase
Said no? Turn it on later:
hermes plugins enable unibaseio-membase
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).
Local Markdown vault for Hermes Desktop — notes, wikilinks, search, recycle bin, and an interactive graph.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install brain-graph
Said no? Turn it on later:
hermes plugins enable brain-graph
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Cognee
Community
Knowledge-graph memory for Hermes, shared with Cognee's Claude Code, Codex and OpenClaw plugins: automatic recall, remember, forget, recaps and code search, on a local cognee server or Cognee Cloud.
Knowledge-graph memory for Hermes, shared with Cognee's Claude Code, Codex and OpenClaw plugins: automatic recall, remember, forget, recaps and code search, on a local cognee server or Cognee Cloud.
Good to know before installing
Runs a local cognee server (uvicorn on 127.0.0.1:8011) and a session-close watcher in the background; each turn plus its tool calls and results (redacted, capped) go to that server and on to your configured LLM provider (OpenAI by default), or to Cognee Cloud / COGNEE_BASE_URL in remote mode; turns the server could not take are queued in ~/.cognee-plugin; the store lives in ~/.cognee, outside HERMES_HOME and shared across profiles and with Cognee's Claude Code, Codex and OpenClaw plugins; cognee sends anonymous telemetry unless TELEMETRY_DISABLED=1.
From the plugin's 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 cognee
Said no? Turn it on later:
hermes plugins enable cognee
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Pdf Surgeon
Community
Model-driven editor of PDF text whose result keeps the original typesetting, by rewriting the page content stream in place — the string operand inside the existing BT/ET block is replaced and the Tm origin of…
Model-driven editor of PDF text whose result keeps the original typesetting, by rewriting the page content stream in place — the string operand inside the existing BT/ET block is replaced and the Tm origin of everything after it on the line is retargeted, so font, size, colour, baseline, char/word spacing, horizontal scale and kerning survive untouched because they are never rewritten. This is the alternative to redact-and-re-stamp, which defaults to Helvetica 8pt and makes you restate font, size and colour by hand; get any of that wrong and the page reads as forged. The phrase must match exactly (whitespace is ignored); a fuzzy match is refused rather than allowed to edit text the caller never named. Until an edit is accepted the output is written under a temporary name next to the destination and moved into place only after verification passes, so a failed check leaves nothing behind; the destination must end in .pdf, must not already exist, must not resolve to the input, and must have an existing parent directory, because the path arrives from the model. Verification enforces that the edited line reads exactly as the original with the phrase swapped and nothing else, that every other line on the page is unchanged, that block count, baseline, font, size and spacing hold, that the old phrase's occurrence count dropped by exactly one (allowing for copies inside the replacement), and that the page's font/size/colour set is unchanged; a pixel-diff band is reported for information and does not decide the outcome. Refuses, writing nothing, on scans, Type3/XObject text, pages with more than one content stream, and a replacement needing a glyph the embedded subset lacks — it never falls back to substituting a typeface. Widths are measured from the embedded font program, not the system font of the same name. action="inspect" lists each line with its baseline and BT/ET block count so a caller can tell whether a document is editable before choosing what to replace. Requires a digital-born PDF whose text is laid out as one block per word/run with an explicit Tm origin (Word, LibreOffice, Excel, Google Docs).
Good to know before installing
This can alter documents such as certificates or invoices; use it only on documents you are entitled to change. The edit is not visible on the page and not recorded in the Info dictionary. It is detectable at file level: the PDF is re-saved by PyMuPDF as a single revision, so the file hash and the second trailer /ID change, any earlier incremental-save history is dropped and any digital signature no longer validates. Writes only a new .pdf that does not exist yet and never touches the input. No network, credentials or subprocesses. Depends on PyMuPDF (AGPL-3.0), which Hermes installs for this plugin. Output files inherit the 0600 mode of the temporary file they are moved from.
From the plugin's 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 pdf-surgeon
Said no? Turn it on later:
hermes plugins enable pdf-surgeon
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).
Encrypted, fully offline memory provider. AEAD-encrypted local vault (vectors included), bundled embedding model, exact hybrid search, no API key and no network at runtime. One vault shared with Claude, Cursor and any other MCP client on the machine.
Good to know before installing
Installs the full compartment engine (about 27 Python packages including onnxruntime, tokenizers, mcp and system-tray dependencies) into the Hermes venv; the provider's system prompt instructs the model to store passwords and API keys in the encrypted vault.
From the plugin's 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 compartment
Said no? Turn it on later:
hermes plugins enable compartment
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).
Create, clean, and verify standalone Markdown with conservative semantic repair and deterministic artifact checks.
Good to know before installing
Skill-only plugin that has the agent run its bundled Node.js 22+ scripts through the terminal; on first use it runs `npm ci` in the plugin folder (lockfile-pinned packages from registry.npmjs.org), and the optional `/wolfmarkdown setup` also creates skill symlinks in ~/.agents/skills and ~/.claude/skills.
From the plugin's 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 wolfmarkdown
Said no? Turn it on later:
hermes plugins enable wolfmarkdown
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
SuperLocalMemory
Community
Local-first long-term memory for Hermes, kept on your own computer: recall before each turn, tool-outcome logging, opt-in turn capture, 16 skills and /slm commands.
Local-first long-term memory for Hermes, kept on your own computer: recall before each turn, tool-outcome logging, opt-in turn capture, 16 skills and /slm commands.
Good to know before installing
Talks only to the `superlocalmemory` MCP server you configure and grant in `plugins.entries.superlocalmemory.mcp_allowlist` (on this computer, or on another one with `connection: remote`): each turn's user message (redacted) is sent for recall and every tool call's arguments and result (redacted, up to 2,000 characters each) are logged to it, and with `capture_turns` on every turn is saved; `/slm` commands run the local `slm` CLI, including ones that change SLM and host settings (`/slm upgrade-hosts --apply` writes the plugin's grant into Hermes config.yaml); `slm_agent` starts a child agent that inherits the parent session's tools.
From the plugin's 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 superlocalmemory
Said no? Turn it on later:
hermes plugins enable superlocalmemory
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).
Profile-scoped document OCR for Hermes Desktop and HUD, with a guarded per-profile Windows service.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install document-reader
Said no? Turn it on later:
hermes plugins enable document-reader
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Hermes Dreaming
Community
Nightly deterministic memory consolidation ("dreaming"): corroborates candidate facts with what humans actually said on distinct days, proposes the few worth keeping with a verbatim edit anchor, asks whether stale…
Nightly deterministic memory consolidation ("dreaming"): corroborates candidate facts with what humans actually said on distinct days, proposes the few worth keeping with a verbatim edit anchor, asks whether stale memory entries still hold, and wakes the agent only when there is work — including a memory file close to its char limit. Fact sources: the holographic store, a SQLite or JSONL export, or none. Secrets and instructions are screened by the dream's own rules plus a verbatim copy of the holographic plugin's screen (scripts/holo_screen.py, MIT, same maintainer), applied to stored facts and human messages before anything reaches memory, the report or the model. Portable Agent Plugins v1 package (plugin.json + skills/); no tools, hooks, middleware or env vars.
Good to know before installing
By default the scripts make no network or LLM calls and open state.db and every fact store read-only (SQLite mode=ro; with holographic >= 0.15.0 including its fact_versions/fact_confirmations tables, to say who stands behind a fact); they also read Hermes config.yaml's memory/timezone keys and the holographic plugin's db_path/scope/cron_writes/min_trust_threshold (the floor recall applies, so a rejected fact is only reported when the store still trusts it) and, to say so in install.py --check, embeddings/mirror_memory_writes, the pending/memory approval queue, cron/jobs.json (to find their own jobs) and — only when chat_stores is set, with holographic scope user/chat/thread — the per-chat databases next to the store (counts of every one; facts of the chats listed in promote_from). An optional cloud judge (judge in dreaming.json, off by default; off, its code is not even loaded) may, once the owner enables it, send for each mention the rules counted the fact's text and that person's own words (no reply quote, link, id, sender or time; names inside the text may be included; screened for secrets and instructions first), only from the chats, sources and chat stores the owner lists, ove
From the plugin's 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 hermes-dreaming
Said no? Turn it on later:
hermes plugins enable hermes-dreaming
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Hermes Artifacts
Community
Private library for the finished documents agents make (self-contained HTML, Markdown, SVG, PNG, WebP), with an Artifacts dashboard tab and explicit, expiring, revocable guest links for one artifact each.
Private library for the finished documents agents make (self-contained HTML, Markdown, SVG, PNG, WebP), with an Artifacts dashboard tab and explicit, expiring, revocable guest links for one artifact each. Early public preview.
Good to know before installing
The plugin is a client of a separate Artifacts service you run yourself from the same repository (not installed by the plugin): six tools and the dashboard tab send artifact bytes and metadata to HERMES_ARTIFACTS_URL with the machine credential HERMES_ARTIFACTS_TOKEN, resolved through Hermes secret scope, held server-side and never sent to the browser. artifact_publish reads a resolved local path only after Hermes read-policy and supported-extension checks; an explicit kind must match. artifact_download checks raw and resolved destinations against Hermes write policy, refuses approval-required paths even with overwrite=true, and writes atomically through a temporary sibling. File policy is defense in depth, not filesystem isolation. Sharing creates a public bearer link on your service; revocation cannot recall copies. Stores no data and no credentials of its own; no hooks, background processes or telemetry.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs HERMES_ARTIFACTS_URL, HERMES_ARTIFACTS_TOKEN), then asks whether to turn it on.
hermes plugins install artifacts
Said no? Turn it on later:
hermes plugins enable artifacts
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Deja Memory
Community
Memory from the coding sessions already on this machine — Claude Code, Codex, Cursor, Hermes and the other agents deja reads, including history from before it was installed.
Memory from the coding sessions already on this machine — Claude Code, Codex, Cursor, Hermes and the other agents deja reads, including history from before it was installed. No model, no API key, no server.
Good to know before installing
Runs the separately installed, unpinned deja binary (brew install deja-vu) as a subprocess; deja reads Claude Code, Codex, Cursor, Hermes and other agents' local transcript files, keeps its index under ~/.cache/deja, and recalled text from those agents is injected into Hermes turns; nothing leaves the machine.
From the plugin's 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 deja-memory
Said no? Turn it on later:
hermes plugins enable deja-memory
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).
Convert one local file to Markdown with doc_convert on Linux and macOS, built on Microsoft's MarkItDown. Microsoft and MarkItDown are trademarks of the Microsoft group of companies.
Good to know before installing
The doc_markdown toolset is on by default on every surface, including a gateway, so anyone you allow there can call doc_convert; stop it with hermes tools. It does not fetch pages. Unattended sessions still convert when Hermes calls the tool. This plugin creates no cron job. A child process runs MarkItDown with no Hermes keys in its environment; on macOS the plugin runs ps about every 10 ms to watch that child's memory. It stops 8 seconds after its converters load, at 60 seconds if loading never finishes, or above 922746880 bytes. It is not a sandbox: after realpath it may read any allowlisted path it can open. Unpublished Hermes code locates the Hermes home, and a failed check refuses the path. Removal deletes the plugin directory, not the markitdown package. Windows was not tested.
From the plugin's 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 doc-markdown
Said no? Turn it on later:
hermes plugins enable doc-markdown
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Sgme
Community
SGME (拾光记忆) self-hosted long-term memory engine — tagged memories with provenance, per-turn recall, automatic session refinement, a skills library, wiki knowledge base, care signals, communication roles and a…
SGME (拾光记忆) self-hosted long-term memory engine — tagged memories with provenance, per-turn recall, automatic session refinement, a skills library, wiki knowledge base, care signals, communication roles and a three-pool task system (ideas/demands/projects), all behind one HTTP service you own. The plugin is a thin bridge: no LLM, no database, everything heavy runs in your SGME server (local or remote).
Good to know before installing
The plugin talks only to the SGME server you configure (default http://127.0.0.1:9910, SGME_BASE_URL for a remote server), sending SGME_AGENT_KEY / SGME_ADMIN_KEY read through Hermes's secret scope; each session's user, assistant and tool messages are appended to that server and refined into memories at session end by an LLM you configure on the SGME side; its sgme_* tools let the model read and change memories, skills, wiki pages and tasks on that server and write skill packages under $HERMES_HOME/plugin-data/sgme/skills/ on the SGME host; credential names in the SGME vault can be listed, and reading a credential value into the conversation is off by default (credential_get_enabled / SGME_ENABLE_CREDENTIAL_GET); no third-party services, no telemetry.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs SGME_BASE_URL, SGME_AGENT_KEY, SGME_ADMIN_KEY, SGME_INJECT_MODE, SGME_INJECT_MAX_TOKENS, SGME_CAPTURE_ENABLED, SGME_REFINE_ON_END, SGME_HERMES_AGENT_ID, SGME_HTTP_TIMEOUT), then asks whether to turn it on.
hermes plugins install sgme
Said no? Turn it on later:
hermes plugins enable sgme
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).
Publish and read private Markdown or HTML reports through your Artifact Relay server.
How to install
Install it. Hermes asks for any API keys it needs (this one needs ARTIFACT_RELAY_API_TOKEN), then asks whether to turn it on.
hermes plugins install artifact-relay
Said no? Turn it on later:
hermes plugins enable artifact-relay
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).
HyAtlas 5 — self-hosted 8-layer memory provider backed by a pure-Go single-binary server you run yourself (chromem-go vectors, in-process BGE-small embeddings, hybrid vector + keyword search, bitemporal knowledge graph with source citations). Embeddings, the vector index and stored memories are kept locally. Ships agent tools (hyatlas_status/search/recent/add), a `hermes hyatlas` CLI, a Desktop pane with a starmap graph view, and a web dashboard.
Good to know before installing
Requires the separate hyatlas-go server, installed by the user. The plugin never downloads or bundles it, and it talks only to the configured server (default 127.0.0.1:19528). Embeddings are computed locally; stored memories leave the machine only in the LLM calls described below. Extraction is opt-in and uses an LLM you choose: `hermes memory setup` asks for any OpenAI-compatible endpoint, model and key, and stores the key in Hermes's .env as HYATLAS_LLM_KEY. The plugin reads that key only through Hermes's get_secret and reads no Hermes credential. A plain key file named by HYATLAS_LLM_KEY_FILE also works; the server reads it on every call, so do not point it at another program's credentials such as Hermes auth.json. The server has no default endpoint and makes no LLM call until the endpoint, the model and a key are all present; while the endpoint and model are set but no key has arrived, /api/v1/status reports llm "awaiting_key". `hermes memory setup`, the repo installer and the sample launcher pre-fill a free Nous Portal endpoint and model (and setup defaults to ultra mode), but nothing is sent until a key is supplied. A server the plugin starts gets that key in its environment;
From the plugin's 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 hyatlas
Said no? Turn it on later:
hermes plugins enable hyatlas
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).
Long-term memory for Hermes agents, stored in a local SQLite database. FTS5 full-text search with optional vector (sqlite-vec) recall, importance-weighted decay, a queryable memory graph, and automatic capture: a declarative rule engine classifies corrections, constraints, preferences, decisions, and agent-discovered facts from a conversation and stores each one as a distilled, self-contained fact. Runtime notifications and read-only OpenLTM tool requests are excluded by named guards so ops noise never becomes memory. No cloud, no telemetry, no API keys required; optional semantic recall via a local llama.cpp embedding server. MIT licensed.
Good to know before installing
Local SQLite in HERMES_HOME; runs git config to read the repo remote; memory text goes to Gemini or OpenAI embeddings, or to the llama.cpp server URL you set (default 127.0.0.1:8080), only if selected in openltm.json (default local Ollama)
From the plugin's 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 openltm
Said no? Turn it on later:
hermes plugins enable openltm
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).
Local-first long-term memory and memory-aware context compression for Hermes — SQLite, no account, API key or hosted service required. Captures every turn durably, extracts beliefs with provenance, answers from memory (raw-tier fallback and abstention), derives scoped conclusions, and compresses the context window losslessly with a restorable record. Registers the memory-provider AND context-engine slots from one shared core, and ships the Tapestry dashboard.
Good to know before installing
Off-host embedding endpoints are refused by default (RFC1918/ULA/CGNAT and https peers); sending memory excerpts off the host requires opting in via embeddings.allow_remote. Disclosure — the git mirror (engine/gitmirror.py) is on by default and writes plaintext JSONL copies of memory into a local git repo at ~/.hermes/commons/db/chronicle/git; it pushes only when git_remote is configured, and its 'encryption' option is a repeating-key XOR obfuscation, not cryptographic encryption.
From the plugin's 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 chronicle
Said no? Turn it on later:
hermes plugins enable chronicle
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).
Independent Hermes integration of Victor Taelin's OptMem design: local, append-only memory with regex/BM25 recall and a bounded wake digest. Hybrid and guarded OptMem-only modes; verified migration and rollback. Local by default. Compaction is manual unless auto_nap is enabled. Optional LLM summaries run only when both auto_nap and llm_summary are on; they send memory blocks to the configured provider via host-owned authentication and may incur token costs. Summaries are lossy, raw records remain recoverable, and conflicts are not resolved automatically. Wake consumes model context. See README for upstream attribution.
Good to know before installing
Memory is stored locally under HERMES_HOME; optional auto_nap+llm_summary sends stored memory lines to the user's configured model provider; the optmem-only mode (explicit CLI with --yes) disables Hermes' built-in MEMORY.md/USER.md injection after a verified backup.
From the plugin's 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 optmem-hermes
Said no? Turn it on later:
hermes plugins enable optmem-hermes
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).
Local long-term memory for Hermes agents. Everything stays on your machine: an SQLite store plus bundled embedding and NLI models, no telemetry, no LLMs. Limbic is designed on the physiological brain, opaque and organic. Memories strengthen or atrophy with use, corrections replace what they superseded — all deterministic background mechanisms, zero LLM calls. Algorithmic forgetting keeps atrophied memories out of the database. Recall is calibrated: when nothing in memory is confident enough, it abstains instead of guessing, so the agent answers honestly rather than surfacing near-misses. First start downloads ~1 GB of pinned models once, then runs fully offline. PolyForm Noncommercial 1.0.0 (commercial use requires a separate license).
Good to know before installing
The agent-facing tools are remember, recall and forget (forget lists candidate facts for a query, then deletes the one fact id the user picks, scoped to the current user, and appends a hash-only receipt of the content's sha256, length, user id and fact id to limbic.db.deletions.jsonl beside the database); on first primary session start downloads ~1.0GB of ONNX models (Arctic Embed 2.0 L int8 embedding, ~570MB; MiniLMv2 NLI, ~430MB, on first contradiction check) from huggingface.co at pinned commits with hash checks into ~/.cache/limbic/ (outside HERMES_HOME; %USERPROFILE%\.cache\limbic on Windows); at every model load, every file in those cache folders that is not in the pinned manifest is deleted — including unrelated files if you point embedding/nli cache_dir at a shared folder; spaCy NER models are optional: `hermes limbic languages --set <lang>` and `hermes limbic setup` run `python -m spacy download <model>`, which pip-installs each model package (~14.5MB, version picked by spaCy, not hash-pinned) from spaCy's GitHub releases into Hermes's own Python environment, and `hermes limbic setup` also pre-downloads both ONNX models; memory stays local in limbic.db under HERMES_HOME, f
From the plugin's 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 limbic
Said no? Turn it on later:
hermes plugins enable limbic
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).
Lossless memory for long sessions: LCM-X keeps every turn in a local store instead of compacting it away, and the agent can search and expand it. The store is local SQLite (lcm.db) with a recoverable DAG of summaries over it and 15 lcm_* tools for search, recall and expansion. Select it with context.engine: lcm-x. Upgrading from hermes-lcm (breaking in v0.24.0): stop Hermes, then in plugins.enabled replace hermes-lcm with hermes-lcm-x and run exactly one LCM copy (the install script prints the steps; the old engine name lcm still resolves with a deprecation warning); lcm.db and the lcm: config block are unchanged. Summaries use the model Hermes is configured with.
Good to know before installing
Optional semantic recall (embeddings_enabled, off by default) sends message text to the embedding provider you configure (Voyage via VOYAGE_API_KEY, an OpenAI-compatible endpoint, or a local Ollama), and once enabled new summaries are embedded automatically in the background; in-process FastEmbed keeps it on the machine after a one-time model download. For known cloud providers the provider-bound copy is privacy-transformed by default (LCM_EMBEDDING_PRIVACY_ENABLED=false opts out), while lcm.db keeps the raw text. Every turn (user, assistant and tool output) is stored in plaintext in lcm.db (secret redaction at rest is opt-in), and oversized tool outputs are by default written as plaintext files under HERMES_HOME/lcm-large-outputs and replaced in the model's context by recoverable references. The engine also reads Hermes' state.db read-only for session lineage, reads private AIAgent attributes via the call stack on Hermes builds without subagent hooks, and runs git on its own install directory for lcm_status/lcm_doctor; tiktoken may fetch its BPE file on first use.
From the plugin's 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 hermes-lcm-x
Said no? Turn it on later:
hermes plugins enable hermes-lcm-x
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Agentplaybooks Memory
Community
Private AgentPlaybooks memory for Hermes: bounded keyword recall across personal and team sources, exact native memory-write mirroring, archive and history.
Private AgentPlaybooks memory for Hermes: bounded keyword recall across personal and team sources, exact native memory-write mirroring, archive and history.
Good to know before installing
Keywords derived from each turn's query are sent to the configured AgentPlaybooks service for recall from your personal and configured team playbooks; explicit native memory writes are mirrored there. Defaults to agentplaybooks.ai over HTTPS; localhost HTTP is supported, and remote intranet HTTP requires an explicit opt-in that sends the API key unencrypted. Team and shared playbooks are configured explicitly: the agent can write, archive and permanently delete entries in configured team playbooks (shared playbooks are read-only), and teammates' entries are recalled into context.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs AGENTPLAYBOOKS_MEMORY_API_KEY), then asks whether to turn it on.
hermes plugins install agentplaybooks-memory
Said no? Turn it on later:
hermes plugins enable agentplaybooks-memory
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Memory Shield
Community
Keeps your agent from rewriting or wiping what it remembers about you: by default the agent may add facts to the owner profile (USER.md) wherever it may write and may correct one only when the owner asks in a direct…
Keeps your agent from rewriting or wiping what it remembers about you: by default the agent may add facts to the owner profile (USER.md) wherever it may write and may correct one only when the owner asks in a direct chat, the CLI or a trusted chat, and nobody may delete one; the agent's notes (MEMORY.md) cannot be deleted; group chats are read-only except for the people and owner-only chats you trust, and once trusted_users is set a direct chat with anyone not listed is read-only too; Hermes' unattended background review may not touch the owner profile. Block, ask through Hermes' approval prompt or just log, and undo edits and deletions from snapshots.
Good to know before installing
No network calls, credentials, shell commands or background processes. One pre_tool_call hook reads the turn's platform, chat type, chat id and name, sender id and name and the cron flag (gateway.session_context) and whether the run is Hermes' unattended review (tools.skill_provenance.is_unattended_review), checks memory tool calls, and checks write_file, patch, terminal and execute_code calls only for a write into, or a removal of, USER.md, MEMORY.md or the memory folder (reading a memory file or copying it elsewhere passes in calls up to 16 KB; a longer call that names them is refused); mode approve asks through Hermes' approval gate in the owner's direct chats and the CLI and blocks in shared chats, cron and direct chats with people not in trusted_users. Writes plugin-data/memory-shield/audit.jsonl (the last 500 refused or flagged writes: time, chat, sender and a 160-character excerpt) and snapshots/ (full copies of USER.md and MEMORY.md taken right before an allowed edit or deletion, 20 per file by default). Reads the memory files and holds the memory store's lock files while it reads or writes them (not on Windows); /memory-shield restore overwrites one memory file. /memory-sh
From the plugin's 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 memory-shield
Said no? Turn it on later:
hermes plugins enable memory-shield
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).
Supermemory semantic long-term memory provider — profile recall, semantic search, explicit memory tools, and per-turn conversation capture. Maintained by Supermemory; the same provider that shipped in-tree.
How to install
Install it. Hermes asks for any API keys it needs (this one needs SUPERMEMORY_API_KEY), then asks whether to turn it on.
hermes plugins install supermemory
Said no? Turn it on later:
hermes plugins enable supermemory
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Honcho Memory
Community
Desktop workbench for the Honcho memory behind the focused chat: read the newest conclusions, trace their premises, search messages, ask scoped questions, and add confirmed corrections or source files.
Desktop workbench for the Honcho memory behind the focused chat: read the newest conclusions, trace their premises, search messages, ask scoped questions, and add confirmed corrections or source files. Uses each profile's existing Honcho provider configuration.
Good to know before installing
Talks only to the Honcho server each profile is already configured for, through Hermes's own Honcho client and credentials, and polls it about every 10 seconds for the focused chat while Desktop is open. Ask runs a Honcho reasoning call that may use credits. Add fact/correction and Add to session write to Honcho only after you confirm the target in a dialog; Add to session uploads the text or PDF/JSON/text file you choose. A chat from another local profile is read with that profile's own Honcho configuration, only where this plugin is enabled. It reads the focused chat's title and folder from the profile's session database, read-only. No telemetry.
From the plugin's 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 hermes-honcho-plugin
Said no? Turn it on later:
hermes plugins enable hermes-honcho-plugin
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Memory Pane
Community
A Hermes Desktop pane for the built-in memory: see what the focused chat remembered, updated or forgot, and edit, delete or undo any entry without leaving the conversation.
A Hermes Desktop pane for the built-in memory: see what the focused chat remembered, updated or forgot, and edit, delete or undo any entry without leaving the conversation. Works alongside the built-in memory; not a memory provider.
Good to know before installing
A tool_execution middleware reads MEMORY.md and USER.md around each memory call and logs the entry-level changes to $HERMES_HOME/plugin-data/hermes-memory-pane/; the pane rewrites memory entries only when the user edits, deletes, adds or undoes one, through Hermes's own memory store; no network, credentials, shell commands or background processes.
From the plugin's 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 hermes-memory-pane
Said no? Turn it on later:
hermes plugins enable hermes-memory-pane
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Memex8
Community
Self-hosted vector memory (Qdrant + TurboQuant compression) with auto-discovered knowledge realms, semantic search across conversations and ingested documents, and a slumber pipeline for memory consolidation.
Self-hosted vector memory (Qdrant + TurboQuant compression) with auto-discovered knowledge realms, semantic search across conversations and ingested documents, and a slumber pipeline for memory consolidation. v1.1.0 adds optional per-session injection dedup with char-budget gate, decision/evaluation memory-type promotion (slower decay for load-bearing turns), prompt-injection sanitization on read, configurable system-prompt template, export/import memories as JSON, and a /memex8 slash command. New memory behaviours are opt-in; /memex8 export|import is confined to $HERMES_HOME/plugin-data/memex8 unless enable_export_import=true.
Good to know before installing
Auto-stores a truncated copy (first 300 chars) of every user and assistant turn, plus per-message previews of the whole transcript at session end and before context compression, to the memex8 server at MEMEX8_BASE_URL (self-hosted; default http://localhost:8080) using MEMEX8_API_KEY.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs MEMEX8_API_KEY), then asks whether to turn it on.
hermes plugins install memex8
Said no? Turn it on later:
hermes plugins enable memex8
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).
Long-term memory for Hermes, backed by HydraDB. Relevant context is recalled before each turn, and completed turns are saved in the background.
Good to know before installing
When selected as the memory provider, each turn's user message (as the recall query) and every completed user/assistant turn are sent over HTTPS to the HydraDB API (api.hydradb.com, or HYDRADB_BASE_URL) under HYDRADB_API_KEY.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs HYDRADB_API_KEY, HYDRADB_DATABASE), then asks whether to turn it on.
hermes plugins install hydradb
Said no? Turn it on later:
hermes plugins enable hydradb
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).
Hosted memory for Hermes with a full history: see what your agent remembered, when it changed and why. Recalls relevant memories before each turn, adds bilinc_recall, bilinc_remember, bilinc_revise and bilinc_forget tools, and mirrors Hermes built-in memory writes. Maintained by ReARC Labs; free plan available.
Good to know before installing
Recall queries (the text of each message, when auto_recall is on), tool arguments, mirrored built-in memory writes, the Hermes session id and, only if memory.bilinc.capture_turns is turned on, each turn's user and assistant text are sent over HTTPS to bilinc.space under your BILINC_API_KEY; requests carry User-Agent bilinc-hermes/<version> and X-Bilinc-Client: hermes-plugin headers. Secret-looking strings are redacted before sending. Recall and writes run on background threads inside Hermes; no separate process, local database or telemetry.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs BILINC_API_KEY), then asks whether to turn it on.
hermes plugins install bilinc
Said no? Turn it on later:
hermes plugins enable bilinc
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Ctx checkpoint
Community
Memory provider that archives the direct user/assistant transcript into a ctx knowledge store before every compaction, deterministically and with no LLM in the path, and hands the resulting block IDs to the compaction…
Memory provider that archives the direct user/assistant transcript into a ctx knowledge store before every compaction, deterministically and with no LLM in the path, and hands the resulting block IDs to the compaction summary so the exact wording stays recoverable. Best-effort on any supported Hermes; with compression.checkpoint_required on Hermes 0.21.1+ it uses the fail-closed pre-compress checkpoint contract (#94639) and blocks compaction until the checkpoint is durable.
Good to know before installing
The turns about to be compacted (tool results and system prompts excluded, secrets redacted twice) are written through Hermes' MCP dispatch to the ctx server you configure in mcp_servers; the plugin holds no credentials, makes no other network calls and has no telemetry; it imports the core modules agent.redact, tools.registry and hermes_cli.config.
From the plugin's 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 ctx_checkpoint
Said no? Turn it on later:
hermes plugins enable ctx_checkpoint
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).
Recall and save decisions, preferences and facts in your Kumiho Cloud workspace. Portable Agent Plugins v1 package with hosted OAuth MCP and six skills.
Good to know before installing
Connects to Kumiho's hosted MCP at https://mcp.kumiho.cloud/mcp (OAuth at control.kumiho.cloud, tokens held by Hermes); memory queries, including an automatic topic lookup near the start of relevant conversations, and approved captures are sent there; the server is marked `trust: untrusted`, so Hermes asks before every tool not annotated read-only. The optional backfill helper reads only files the user names and writes review packets to a new folder; Dream State can create a recurring Hermes cron task when asked (read-only by default). No local server, telemetry or background process.
From the plugin's 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 kumiho-memory
Said no? Turn it on later:
hermes plugins enable kumiho-memory
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).
Review pending Hermes memory writes and inspect, add, edit, delete, or AI-compact stored memory from Desktop.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install magi
Said no? Turn it on later:
hermes plugins enable magi
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).
Checkbox staged memory writes and approve or reject the selection from a dialog.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install memory-review
Said no? Turn it on later:
hermes plugins enable memory-review
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Nexus
Community
Self-hosted long-term memory on Qdrant: automatic per-turn prefetch and write-back, plus recall/remember/forget, guardrail rules and a knowledge graph; Hermes and any MCP-connected agent share one collection.
Self-hosted long-term memory on Qdrant: automatic per-turn prefetch and write-back, plus recall/remember/forget, guardrail rules and a knowledge graph; Hermes and any MCP-connected agent share one collection. Embeddings run fully local by default (sentence-transformers with Qwen/Qwen3-Embedding-0.6B, 1024d, about 1.2 GB from Hugging Face on first use; on Apple Silicon the model is pinned to the CPU, because PyTorch's MPS backend aborts the whole process under two overlapping encodes). A cloud embedder runs only when NEXUS_EMBEDDING_PROVIDER names it and its key is present, and a key that merely sits in the environment never selects one. Access levels fail closed: a memory, a protection rule or a graph label without a known level counts as the most restrictive. A local service on 127.0.0.1:9122 serves embeddings and the full MCP toolset; its /embed and /mcp routes demand a per-installation key (service_auth.key, mode 0600) and reject non-loopback Host/Origin, while the open /healthz answers liveness only. The plugin starts that service when Hermes cannot load the embedding stack, and it keeps running afterwards. Session-end fact extraction sends conversation text to the model endpoint from Hermes config.yaml, and the consolidation daemon to its configured model, which defaults to Hermes's own default model through local Ollama; reads ~/.hermes/.env and config.yaml; state and daily backups under ~/.nexus-memory; NEXUS_UPDATE_CHECK=1 opts into a GitHub release check.
Good to know before installing
When Hermes cannot load the embedding stack (and always on Apple Silicon unless NEXUS_EMBED_IN_HOST=1), the plugin starts `nexus-memory serve` on 127.0.0.1:9122 (embeddings, the full Nexus MCP toolset and a consolidation daemon that sends memory text to the Ollama endpoint at 127.0.0.1:11434 or NEXUS_OLLAMA_BASE under the model named by NEXUS_CONSOLIDATION_MODEL, nexus-memory.consolidation_model or Hermes's model.default, which can be an Ollama cloud model), and the service keeps running after Hermes exits; its /embed and MCP routes require a per-install key in ~/.nexus-memory/service_auth.key (0600) and a loopback Host/Origin; session-end fact extraction sends conversation text to the model endpoint in Hermes config.yaml, and the opt-in recall reranker (nexus-memory.rerank or NEXUS_RERANK=1) defaults to sending each query plus up to 20 memory snippets to that same endpoint using the provider API key it reads from config.yaml; reads ~/.hermes/.env and config.yaml; state and daily backups under ~/.nexus-memory; opt-in NEXUS_UPDATE_CHECK=1 adds a GitHub release check and an upgrade nudge to the system prompt.
From the plugin's 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 nexus
Said no? Turn it on later:
hermes plugins enable nexus
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).
Durable native memory for Hermes with LLM fact extraction. Conversations are distilled by the Hermes-configured LLM into searchable memories — facts, preferences and decisions with deduplication and importance — instead of storing turns verbatim, and are kept in Qdrant (embedded, self-hosted Server, or Qdrant Cloud) with configurable embeddings (default: local Ollama qwen3-embedding:4b at 2560 dimensions). The plugin registers a native MemoryProvider plus four scoped tools: qdrant_memory_search, qdrant_memory_add, qdrant_memory_update and qdrant_memory_delete. A SQLite WAL admission ledger makes every write idempotent and replayable across restarts with fail-closed recovery; scoped inventory, portable export and scope-aware deletion (list/export/delete-all with explicit single-agent vs all-agents semantics) ship in the same CLI, and `migrate mem0` imports existing Mem0 exports with resumable, verifiable runs.
Good to know before installing
Memory text is stored in the configured Qdrant store (embedded files under <HERMES_HOME>/qdrant-memory/qdrant by default, or the Server/Cloud URL you set), and memory text plus each turn's recall query are sent as plain text to the configured embedding endpoint (default local Ollama at http://127.0.0.1:11434; an OpenAI-compatible remote endpoint can be configured, and keyed endpoints must use HTTPS). Disclosure — after each primary-agent turn, at session end and before context compression, conversation text goes to the LLM configured in Hermes through the Hermes plugin LLM facade (a provider/model override needs the plugin's Hermes trust grant) to extract facts and to compare near-duplicate memories; that LLM may be a remote provider. Disclosure — the provider is selected with memory.provider: qdrant-memory; its settings live in <HERMES_HOME>/qdrant-memory.json (0600, secrets stripped on save). QDRANT_URL, QDRANT_API_KEY and EMBEDDING_API_KEY are read through the Hermes secret scope, but an api_key written by hand into qdrant-memory.json takes precedence, and `migrate mem0` reads the source Qdrant endpoint and any api_key from <HERMES_HOME>/mem0.json or --source-config. Disclosure
From the plugin's 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 qdrant-memory
Said no? Turn it on later:
hermes plugins enable qdrant-memory
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Hwiki
Community
Markdown wiki as Hermes long-term memory: plain files you and the agent edit together (Obsidian-compatible, git-versionable), local SQLite FTS5 search with optional qmd hybrid retrieval.
Markdown wiki as Hermes long-term memory: plain files you and the agent edit together (Obsidian-compatible, git-versionable), local SQLite FTS5 search with optional qmd hybrid retrieval. Inspired by the Karpathy LLM wiki.
Good to know before installing
Reads every Markdown file under the wiki folder you set (wiki_path, outside HERMES_HOME; untrusted_dirs, default raw/, excluded) and injects up to ~1,400 characters of matching excerpts into each turn; the agent appends dated notes only under <wiki>/<memory_dir> (default wiki/memory), and additions to Hermes's built-in memory are mirrored there by default (mirror_builtin_memory), so they land in a folder you may commit or sync; keeps an index at HERMES_HOME/hwiki-index.sqlite and config in HERMES_HOME/hwiki.json, and adds the wiki folder to hermes backup. Cron and subagent runs get read-only recall. No network with the default fts5 backend; the optional qmd backend runs the separately installed qmd CLI (npm @tobilu/qmd, Node ≥22), whose vector modes download local models (~0.3–1.6 GB).
From the plugin's 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 hwiki
Said no? Turn it on later:
hermes plugins enable hwiki
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).
OptChat-style endless memory for Hermes: an append-only verbatim log plus a binary summary tree, exposed as recall through the MemoryProvider ABC. Background compactor builds the tree with a cheap auxiliary model (call_llm task optchat_compact); prefetch returns a fixed-budget view of the whole history; optchat_zoom/optchat_date tools open any line down to the verbatim message.
Good to know before installing
Every turn's user messages, agent replies, tool calls and tool results (each result capped at 30,000 characters, after Hermes's secret redaction) are appended permanently to unencrypted owner-only files under $HERMES_HOME/optchat/, with no deletion or retention limit; a background compactor sends those messages and the surrounding summary view to your auxiliary model route (task optchat_compact) for summarization; each turn injects up to view_budget_chars (default 16,000) of that history into the model context.
From the plugin's 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 optchat
Said no? Turn it on later:
hermes plugins enable optchat
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).
Local-first persistent memory for coding agents. SQLite on your disk - decisions, preferences, error patterns, and guidelines with project and global scopes and guideline-aware search. No cloud, no API key, nothing leaves the machine.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install sugar
Said no? Turn it on later:
hermes plugins enable sugar
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Yantrikdb
Community
Persistent memory for Hermes. Canonicalizes duplicate memories, surfaces contradictions between structured or recognized single-valued claims for review, and returns a why_retrieved reason list with every recall.
Persistent memory for Hermes. Canonicalizes duplicate memories, surfaces contradictions between structured or recognized single-valued claims for review, and returns a why_retrieved reason list with every recall. Embedded by default: no server, no token, no GPU. Optional HTTP backend for HA clusters; pluggable embedders (bundled potion-2M default).
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install yantrikdb
Said no? Turn it on later:
hermes plugins enable yantrikdb
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Memory Rewind
Community
Automatic version history for the built-in memory (MEMORY.md, USER.md), SOUL.md and skills/ (including curator-archived skills): browse, diff and restore any past version with `hermes memory-rewind`, or view it from…
Automatic version history for the built-in memory (MEMORY.md, USER.md), SOUL.md and skills/ (including curator-archived skills): browse, diff and restore any past version with `hermes memory-rewind`, or view it from any chat with the read-only `/memory-history`. Works alongside the built-in memory; not a memory provider.
Good to know before installing
Runs the local git binary (isolated from the user's git config, hooks and signing) to keep a bare repository in $HERMES_HOME/plugin-data/memory-rewind/; reads only the tracked files (never .env, auth.json, databases or skills/.hub/); rewrites tracked files only when the user runs `restore`; no network.
From the plugin's 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 memory-rewind
Said no? Turn it on later:
hermes plugins enable memory-rewind
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).
Self-memory and replacement models for Hermes agents. Remember your work. Train your replacement.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install icarus
Said no? Turn it on later:
hermes plugins enable icarus
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).
Self-owned long-term memory backed by the agent-memory-es service (Elasticsearch). Three agent tools — recall, retain, reflect — over episodic/ semantic/procedural tiers with hybrid BM25+kNN recall and server-enforced private/team/common visibility. Requires a running agent-memory-es instance.
Good to know before installing
Each user prompt (as a recall query), each user message and Hermes memory writes are sent to the agent-memory-es service at AMES_SERVICE_URL (default localhost:8123) with AMES_SERVICE_KEY; the model may store facts in shared team/common visibility tiers.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs AMES_SERVICE_URL, AMES_SERVICE_KEY), then asks whether to turn it on.
hermes plugins install agent_memory_es
Said no? Turn it on later:
hermes plugins enable agent_memory_es
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
No plugins match that search.
Read before you install
Plugins run code inside your agent. Official plugins come from Nous Research's own repo. Community plugins are independent projects, so check the source, the permissions they ask for and any API keys they need. New to plugins? Start with skills vs plugins vs MCP.
