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.
117 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.
Memtomem
Community
Markdown-first long-term memory shared across your coding agents: a local memtomem MCP server plus six memory skills (index, recall, remember, search, setup, status).
Markdown-first long-term memory shared across your coding agents: a local memtomem MCP server plus six memory skills (index, recall, remember, search, setup, status). Notes live in ~/.memtomem and are searchable from Hermes, Claude Code, Codex CLI and Kimi Code. Runs at user scope.
Good to know before installing
The server is launched with `uvx --python 3.12` and downloaded from PyPI (memtomem[onnx]==0.6.9) on first start, with Python 3.12 if uv cannot find one; it runs as a stdio MCP server for the session and reads the directories you ask it to index. With a fresh BM25-only configuration nothing else leaves the machine; an existing memtomem configuration may enable Hugging Face model downloads, a remote embedding or LLM provider, Cohere reranking or search webhooks. At startup the server also reads the nearest .env found upward from its installed location inside uv's cache (normally ~/.env), setting variables not already present, outside Hermes's MCP environment filtering.
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 memtomem
Said no? Turn it on later:
hermes plugins enable memtomem
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).
Dense semantic memory for Hermes, stored in a Qdrant collection you host. Each turn becomes one point — user and assistant text verbatim, no LLM summarization step — embedded on-device at 384 dimensions with fastembed (ONNX; the default install is 206 MB of runtime dependencies with no torch, versus ~1.2 GB when sentence-transformers was a hard dependency) and recalled by cosine search with an optional session_id payload filter, so a result quotes what was actually said. Registers 7 tools: qdrant_search, qdrant_upsert, qdrant_recall, qdrant_collect, qdrant_prepare, qdrant_forget (point-targeted deletion, dry-run by default, no delete-all), and md_search (local markdown knowledge index). An optional recall-indicator display, display.level (off | summary | verbose, default off), adds latency and collection to the chat indicator at summary and one numeric line per operation to the log at verbose — numbers and identifiers only, never recalled message text or search-result snippets (the md_search line also echoes the query you searched — your own input, not recalled content); it is separate from the older top-level progress knob (off | minimal | verbose), which gates status events. sentence-transformers is selectable on GPU hosts; both backends produce identical vectors for all-MiniLM-L6-v2, so switching backends needs no re-embedding. A circuit breaker (5 consecutive I/O failures, 120 s cooldown) degrades to no new memories instead of crashing, and is_available()/check_backend()/unavailable_reason() distinguish a misconfiguration from a dead server. Optional hybrid dense+sparse RRF search (default off): one config key enables dense+BM25 RRF fusion. A fresh collection declares the sparse vector at creation and an existing dense-only store gets it added in place (Qdrant >= 1.18) with one bundled backfill command; measured +0.024 recall@10 on the LongMemEval 1,000-example benchmark. INT8 quantization is not implemented. Local embedded Qdrant mode is not supported: the provider is REST-only and needs a reachable server.
Good to know before installing
All memory content (verbatim user and assistant turns) is stored in and read back from the Qdrant server at the configured url (default http://localhost:6333); QDRANT_API_KEY is only needed for Qdrant Cloud, is kept in .env and read through the Hermes secret scope, and is never written to config.yaml or qdrant.json. Disclosure — the only other outbound traffic is a one-time download of the embedding model weights (plus the 10 MB Qdrant/bm25 sparse model when hybrid is on) from huggingface.co (fastembed falls back to storage.googleapis.com/qdrant-fastembed if that fails); embedding runs on-device and no memory content goes to any other party. Disclosure — settings are stored in <HERMES_HOME>/qdrant.json (created 0600, no credentials) and last-operation status in <HERMES_HOME>/qdrant-status.json. Disclosure — md_search returns snippets of local markdown to the model from ~/.hermes/skills, the Obsidian vault at ~/Documents/hermes_default, ~/.hermes/hermes-agent/website and any path in the md_docs_roots key of qdrant.json; its index is built only when you run scripts/md_ingest.py and lives in <base Hermes home>/state/md-search/ (shared by all profiles). Disclosure — the optional semant
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
Said no? Turn it on later:
hermes plugins enable qdrant
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).
Git-backed Markdown memory with background curation and model-based recall.
Good to know before installing
Runs a background curation agent with terminal, file-read and patch tools on your configured auxiliary model, fed raw conversation turns; it commits and pushes the memory store to whatever git remotes you configure, and pulls shared submodules at session start; the engine runs via uv run, which fetches pyyaml==6.0.2 from PyPI; an optional dataset file (memory.stack.dataset_enabled, off by default) stores full transcripts locally with no rotation.
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 stack
Said no? Turn it on later:
hermes plugins enable stack
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).
Native XMemo memory provider for Hermes Agent — durable, identity-aware cross-session memory with semantic search.
Good to know before installing
Cloud memory provider: sends each user prompt (for recall and the search tools), model-written memories and mirrored built-in Hermes memory writes, plus a stable install ID, to xmemo.dev (Yonro Co., Ltd.); keeps a local SQLite cache of recalled results and a queue of unsent writes in $HERMES_HOME/xmemo_cache.db, partitioned by a hashed account identity; reads the key from XMEMO_KEY (also MEMORY_OS_API_KEY / MEMORY_OS_MCP_TOKEN) and, if none is set, falls back to the xmemo login token in ~/.config/xmemo/credentials.json (a catalog rule 11 deviation kept for existing users); workflow and destructive tools and timeline capture are off by default and opt-in.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs XMEMO_KEY), then asks whether to turn it on.
hermes plugins install xmemo
Said no? Turn it on later:
hermes plugins enable xmemo
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).
Read-only Hermes Dashboard and Desktop plugin for inspecting built-in, holographic, Mem0, Honcho, Mnemosyne, Hindsight, and ByteRover memory.
Good to know before installing
Reads the active profile's memory files, provider configs and provider API keys (keys are never returned to the UI), and on user action sends search/recall/reflect queries with configured bank/peer/user IDs to the configured Mem0, Honcho and Hindsight endpoints (Hindsight Cloud default api.hindsight.vectorize.io) using those keys; ByteRover queries run the local `brv` CLI; for a local embedded Hindsight setup a contents read may start the `hindsight-embed` daemon; no memory is written.
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-ui
Said no? Turn it on later:
hermes plugins enable hermes-memory-ui
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).
LoreConvo memory provider: cross-surface persistent session memory with search, recall and structured memory items.
Good to know before installing
Stores end-of-session transcripts (truncated, including tool output) and Hermes memory writes in ~/.loreconvo/sessions.db, a store shared across all Hermes profiles and other LoreConvo clients, and injects context from those sessions into each turn; a Pro license enables a one-time Hugging Face embedding-model download; installs the loreconvo package (BUSL-1.1) with lancedb, fastembed and onnxruntime into the Hermes environment.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs LORECONVO_HERMES_PROJECT), then asks whether to turn it on.
hermes plugins install loreconvo
Said no? Turn it on later:
hermes plugins enable loreconvo
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.
Vornik Companion
Community
Vornik as Hermes's hardened broker and long-term memory: Hermes holds no credentials; privileged work runs in operator-approved workflows on your own Vornik daemon.
Vornik as Hermes's hardened broker and long-term memory: Hermes holds no credentials; privileged work runs in operator-approved workflows on your own Vornik daemon.
Good to know before installing
Talks only to the self-hosted Vornik daemon at VORNIK_URL with VORNIK_BROKER_TOKEN (and VORNIK_MEMORY_TOKEN for memory); broker tools let the agent start operator-approved workflows on that daemon (writes are approved by a person in Vornik); when selected as memory provider it sends each turn's user query for recall, mirrors MEMORY.md and USER.md writes to the daemon, and asks the daemon to stop recalling (not delete) a mirrored entry that Hermes removes or replaces (/vornik-memory lists and /vornik-forget forgets what Vornik keeps); artifact tools expose only named outputs allowed by the approved workflow from completed runs and read bounded text or return short-lived binary download links from the daemon; task diagnosis tools (offered only when the daemon advertises companion-progress) return a broker task's execution events and closed error classes as the daemon serves them to a broker key; hermes vornik approvals on writes security.approval.transport (and vornik_companion.approval_namespace) to Hermes config, after which Hermes's own dangerous-command prompts (the redacted command text) are sent through the local vornikctl agent host-approval to the daemon and answered on the p
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs VORNIK_URL, VORNIK_BROKER_TOKEN, VORNIK_MEMORY_TOKEN), then asks whether to turn it on.
hermes plugins install vornik-companion
Said no? Turn it on later:
hermes plugins enable vornik-companion
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.
Conxt
Community
Conxt governed memory provider — recall before each turn (personal, plus a team's approved memories), conversation capture in batches, and tools to search, remember, and propose team memories that a person approves in…
Conxt governed memory provider — recall before each turn (personal, plus a team's approved memories), conversation capture in batches, and tools to search, remember, and propose team memories that a person approves in Conxt before anyone recalls them.
Good to know before installing
Each turn's message (first 500 characters) and the conversation's user and assistant messages are sent to the Conxt API at mcp.conxt.dev (or an https CONXT_BASE_URL you set) with your CONXT_API_KEY; tool results are not sent, but text the assistant repeats is. Every entry Hermes's built-in memory tool adds is also copied to your Conxt memory, and conxt_remember / conxt_propose send the memory text they are given. No telemetry, no shell commands, and nothing is written automatically from cron or subagent runs. Requires a Conxt plan that includes API keys.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs CONXT_API_KEY), then asks whether to turn it on.
hermes plugins install conxt
Said no? Turn it on later:
hermes plugins enable conxt
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.
Identity
Community
View and edit the identity files (SOUL.md, MEMORY.md, USER.md, AGENT.md/HERMES.md) from chat, switch the active profile, and see per-line usage with colour-coded staleness timestamps.
View and edit the identity files (SOUL.md, MEMORY.md, USER.md, AGENT.md/HERMES.md) from chat, switch the active profile, and see per-line usage with colour-coded staleness timestamps. Adds six tools, /identity, /identity-switch and /identity-dashboard commands, and a utilization dashboard pane.
Good to know before installing
Reads and writes the identity files and a line-utilization record inside the selected profile directory under HERMES_HOME, and can change which profile is active; it performs no network I/O and holds no credentials. Disclosure — the model-callable identity_edit tool rewrites SOUL.md/MEMORY.md/USER.md/AGENT.md and identity_switch_profile writes HERMES_HOME/active_profile.
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 identity
Said no? Turn it on later:
hermes plugins enable identity
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.
Post Cortex
Community
Self-hosted long-term memory through a post-cortex daemon (https://github.com/julymetodiev/post-cortex): typed records (decisions, fixed problems, code changes) in an entity graph with local semantic search.
Self-hosted long-term memory through a post-cortex daemon (https://github.com/julymetodiev/post-cortex): typed records (decisions, fixed problems, code changes) in an entity graph with local semantic search. Recalls related records from the profile's workspace before each turn, puts the user card and the workspace's project card in the system prompt, mirrors built-in memory writes as records, and adds post_cortex_search, post_cortex_record and post_cortex_context (graph neighbours and reverse dependencies of named components) plus the post-cortex:memory skill. Records and captured turns carry the author hermes:<profile>. Profiles are mapped to shared workspaces by name glob, so a team of profiles recalls each other's records.
Good to know before installing
Talks only to the post-cortex daemon at the configured URL (default http://127.0.0.1:3737; a remote daemon over plain HTTP should sit on a private network or behind TLS): each non-trivial user prompt (up to 2,000 characters) is sent as a search query, and built-in memory writes and post_cortex_record calls are sent as records; with the opt-in capture setting (off by default) each completed turn of the primary agent is sent too: the user's message (with the sender's display name when Hermes knows it), the final reply, tool names and file paths, never tool output; nothing goes to third parties. Disclosure — the daemon stores records (and captured turns, deleted after its message_retention_days) in its own database and redacts credentials, e-mail addresses, phone numbers and public IPv4 addresses on write. Disclosure — PCX_TOKEN (and optionally PCX_URL) is read through the Hermes secret scope; the only local state is $HERMES_HOME/post-cortex.json (0600, never holds the token). No threads or processes of its own (capture runs on Hermes' sync worker), no shell commands, no deletes in post-cortex; cron and subagent runs never write automatically.
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 post-cortex
Said no? Turn it on later:
hermes plugins enable post-cortex
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 backed by total-agent-memory (TAM) over MCP — saves each completed turn (with a noise filter; TAM's quality gate applies), recalls relevant memories before each turn within a token budget, and adds tam_recall / tam_save tools; optional TAM team server for shared company memory.
Good to know before installing
Local mode starts the separately installed tam binary as a child process per session with an allowlisted environment that carries no credentials: Hermes provider keys (including HF_TOKEN and OLLAMA_API_KEY), TAM_API_TOKEN and any *_TOKEN / *_API_KEY / *_SECRET / *_PASSWORD variable are withheld, and of HF_* / OLLAMA_* only non-secret settings pass (OLLAMA_URL, OLLAMA_EMBED_MODEL, HF_HOME, HF_HUB_OFFLINE); it stores user/assistant turn text plus built-in memory additions (not tool output) in TAM's store, by default outside HERMES_HOME and shared with other agents using TAM; remote mode sends the same text to the user-configured URL with an optional TAM_API_TOKEN bearer token; hermes memory setup tam writes tam.json, TAM_API_TOKEN to .env and memory.provider in config.yaml.
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 tam
Said no? Turn it on later:
hermes plugins enable tam
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.
Wicked Memory
Community
Persistent, wallet-scoped long-term memory for Hermes: remember, semantic recall, versioned update, history and approved hard delete, backed by the hosted Wicked Memory service, plus skills for using it and for…
Persistent, wallet-scoped long-term memory for Hermes: remember, semantic recall, versioned update, history and approved hard delete, backed by the hosted Wicked Memory service, plus skills for using it and for connecting the Wicked MCP server. Works with no setup (a wallet is generated on first use; search uses the service's shared free key).
Good to know before installing
Sends the memory text and search queries the agent chooses to memory.wickedapi.com (or your configured base_url), each request signed by the agent's wallet, plus one GET to /v1/status on first use to read the published community key; stores a generated private key unencrypted in the plugin data dir unless you supply WICKED_MEMORY_PRIVATE_KEY; no shell commands, no background processes, no telemetry; every wicked_memory_forget asks for human approval. The bundled wicked-suite-mcp skill walks you through adding the author's hosted Wicked MCP server (https://mcp.wickedapi.com/mcp, 75 tools, some x402-priced); that server is a separate manual step and is not covered by this pin.
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 wicked-memory
Said no? Turn it on later:
hermes plugins enable wicked-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.
Gbrain Plugin
Community
Community (non-official) plugin wiring GBrain (garrytan/gbrain, MIT) into Hermes as a local memory layer over MCP: /gbrain status command, desktop starter, and per-profile Postgres setup/update/maintenance scripts.
Community (non-official) plugin wiring GBrain (garrytan/gbrain, MIT) into Hermes as a local memory layer over MCP: /gbrain status command, desktop starter, and per-profile Postgres setup/update/maintenance scripts. Not affiliated with upstream.
Good to know before installing
The plugin itself only adds a /gbrain status command and a Desktop pane; GBrain is installed by the user via scripts/setup.sh, which installs bun (curl|bash), an unpinned gbrain from GitHub HEAD, and provisions PostgreSQL with sudo.
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 gbrain-plugin
Said no? Turn it on later:
hermes plugins enable gbrain-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).
Local Markdown memory provider with multilingual lexical recall and profile-local durable notes. Create-only writes are limited to primary agent contexts. Uses published birkin-mnemosyne 0.7.2 with compatible updates below 1.0; no API key, network service or telemetry. Session handoff capture is opt-in. Native Hermes memory files remain separate.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install birkin-mnemosyne
Said no? Turn it on later:
hermes plugins enable birkin-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).
Local-only web dashboard for browsing and visualising Mnemosyne memories, triples, stats, and consolidation history.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install mnemosyne-dashboard
Said no? Turn it on later:
hermes plugins enable mnemosyne-dashboard
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.
Cognition
Community
Cognition session-end memory — facts regex-extracted from your messages at session end, stored in a local SQLite queue and JSON log under one repo label, with fetch-first merge, per-entry provenance, and budgeted…
Cognition session-end memory — facts regex-extracted from your messages at session end, stored in a local SQLite queue and JSON log under one repo label, with fetch-first merge, per-entry provenance, and budgeted prefetch (tools: cognition_search, cognition_status, read-only cognition_dream).
Good to know before installing
Saves verbatim excerpts (up to 400 chars) of your own messages that match preference/decision phrases in plain local files under HERMES_HOME/cognition/ (SQLite queue, JSON commit log) and re-injects them into later prompts sent to your model provider; the author name is read from ~/.gitconfig; the plugin makes no network calls of its 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 cognition
Said no? Turn it on later:
hermes plugins enable cognition
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.
Dexio
Community
Dexio shared-wiki memory. Before each turn, the pages of your Dexio wiki that match the user's message; tools to search, read and write the pages your other agents and team also use.
Dexio shared-wiki memory. Before each turn, the pages of your Dexio wiki that match the user's message; tools to search, read and write the pages your other agents and team also use. Nothing is captured automatically: no transcripts or turn logs. Standard library only; no background threads or local services.
Good to know before installing
With DEXIO_API_KEY set, the first 300 characters of each user message go to the Dexio server (default app.dexio.wiki, or DEXIO_URL) as a search query, tool arguments and the agent's profile name go there on tool calls, and the model is prompted to write, overwrite and edit pages in a wiki shared with the user's team and other agents, without a confirmation step.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs DEXIO_API_KEY), then asks whether to turn it on.
hermes plugins install dexio
Said no? Turn it on later:
hermes plugins enable dexio
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).
Shared fleet memory for Hermes agents: every connected agent learns from all other agents connected to the memory, wherever they run. Sessions across machines and harnesses are distilled into one common brain overnight — what one learns, the whole fleet recalls. Pushes a compact per-turn recall index (entries lazy-load via hicortex_get), injects fresh lessons plus a per-agent standing context block at session start — lesson blocks are delimited and carry an explicit reference-data framing line and provenance header — and exposes the full 9-tool memory surface (search, get, recent, ingest, lessons, index, graph, update, delete) through the shared server. The same server also serves Claude Code, OpenClaw, Pi and opencode agents, so mixed-harness fleets share one brain. Stdlib-only, no pip dependencies. Requires a running Hicortex server (npx @gamaze/hicortex init on any machine); data flow: each user message is sent to your configured Hicortex server for recall (default http://localhost:8787); session distillation runs on the server.
Good to know before installing
Sends every user message (and profile name) to your configured Hicortex server each turn for recall, default http://localhost:8787, plain http with a bearer token is accepted for remote servers with a one-time log warning; the server's standing Identity text and lessons are injected into the system prompt; the model can permanently update or delete shared fleet memories via hicortex_update / hicortex_delete without confirmation.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs HICORTEX_URL, HICORTEX_AUTH_TOKEN), then asks whether to turn it on.
hermes plugins install hicortex
Said no? Turn it on later:
hermes plugins enable hicortex
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.
Brethof Brain
Community
brethof-brain long-term memory provider — the memory's briefing in the system prompt at session start, ambient recall on every turn, every turn archived.
brethof-brain long-term memory provider — the memory's briefing in the system prompt at session start, ambient recall on every turn, every turn archived; one memory shared with the user's other agents (Claude Code, Codex, OpenCode and more). Sends each turn to the user's own brethof-brain memory (on their machine at 127.0.0.1:8610, or hosted at memory.brethof.cloud). Needs a brethof-brain account.
Good to know before installing
Sends every user prompt and each turn's user and assistant text, with your API key, to the brethof-brain server you configure (default a local box at 127.0.0.1:8610; hosted at memory.brethof.cloud), and puts the server's returned briefing and recall text into the system prompt and each turn; reads BRETHOF_BRAIN_* from $HERMES_HOME/.env and ~/.brethof-brain/config.json.
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 brethof-brain
Said no? Turn it on later:
hermes plugins enable brethof-brain
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).
Cashew — persistent thought-graph memory with local embeddings, organic decay, and autonomous think cycles.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install cashew
Said no? Turn it on later:
hermes plugins enable cashew
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.
Provenance Gate
Community
Flags memory and skill_manage writes that state a user decision ("the user decided ...", "用户决定 ...") without the user's own words: each such sentence needs a quote that appears verbatim in text the user typed in this…
Flags memory and skill_manage writes that state a user decision ("the user decided ...", "用户决定 ...") without the user's own words: each such sentence needs a quote that appears verbatim in text the user typed in this session, shares key words with the decision and does not drop a negation. A patch is checked by the text it produces. Observe mode (the default) records flagged writes and `hermes provenance-gate report` lists them; block mode refuses them and tells the model how to fix the write. Measured on an independent blind set of 133 lines: precision 1.000, recall 0.694.
Good to know before installing
Two hooks (pre_llm_call, pre_tool_call); keeps a local copy of the text the user types, with its sender_id and session link, and an evidence log of checked claims under plugin-data/provenance-gate (30-day default retention, `hermes provenance-gate purge`); reads MEMORY.md, USER.md and skill files to reproduce what a patch produces; no network, no credentials, never asks for approval.
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 provenance-gate
Said no? Turn it on later:
hermes plugins enable provenance-gate
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).
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install lancedb
Said no? Turn it on later:
hermes plugins enable lancedb
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: store durable facts once and recall them in any session. Portable Agent Plugins v1 package (mcp.json + skills/): the @mem-os/sdk MCP server (pinned 1.6.26) over npx stdio, plus the mem-os-memory skill covering when to store and when to recall. All data stays in a local SQLite database under the user home directory; no cloud, no telemetry, no API keys. Server cwd is ${PLUGIN_DATA} so nothing is written into the install tree. Needs Node.js and npm on PATH.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install mem-os
Said no? Turn it on later:
hermes plugins enable mem-os
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).
MindGraph — semantic graph memory with hybrid retrieval, goal/decision tracking, and cross-document synthesis.
How to install
Install it. Hermes asks for any API keys it needs (this one needs name), then asks whether to turn it on.
hermes plugins install mindgraph
Said no? Turn it on later:
hermes plugins enable mindgraph
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.
Lumberroom
Community
lumberroom memory provider. One durable store shared with every agent you use, recalled on every turn and written through the engine's own memory_write.
lumberroom memory provider. One durable store shared with every agent you use, recalled on every turn and written through the engine's own memory_write. Self-hosted open-source engine or lumberroom.cloud; OAuth or a static token. Maintained by the lumberroom team.
Good to know before installing
When active, every non-trivial user message (first 1,000 characters) and the absolute git-root path of the working directory are sent on each turn to the configured lumberroom engine, which defaults to https://mcp.lumberroom.cloud (operated by Cybersapien Technologies, India) unless base_url names a self-hosted engine; the model is instructed to store decisions, preferences and facts there through memory_write, the engine's live tool descriptions and server instructions are injected into the system prompt each session, and setup switches off Hermes' built-in MEMORY.md/USER.md store.
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 lumberroom
Said no? Turn it on later:
hermes plugins enable lumberroom
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.
Mnemostack
Community
Persistent agent memory over a mnemostack service or a local Qdrant — hybrid recall (vector + lexical + graph), verbatim capture with self-echo suppression, and soft retraction.
Persistent agent memory over a mnemostack service or a local Qdrant — hybrid recall (vector + lexical + graph), verbatim capture with self-echo suppression, and soft retraction. Multi-tenant when pointed at a shared authenticated service; the tenant is resolved server-side from the service key.
Good to know before installing
The pinned directory is a discovery shim; the provider code installs from PyPI at the version pinned in plugin.yaml pip_dependencies (hermes-mnemostack==1.0.3) into the Hermes venv. Configured via MNEMOSTACK_* env vars; no key is required for a purely local Qdrant setup.
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 mnemostack
Said no? Turn it on later:
hermes plugins enable mnemostack
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 Pubky
Community
Setup helper for managed Pubky agents. The launcher syncs agent state, including conversation database snapshots and portable configuration, to your remote Pubky homeserver.
Setup helper for managed Pubky agents. The launcher syncs agent state, including conversation database snapshots and portable configuration, to your remote Pubky homeserver.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-pubky
Said no? Turn it on later:
hermes plugins enable hermes-pubky
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.
Lancedb Suite
Community
Local-first LanceDB vector memory with a strict write contract, calibrated abstention, typed relations, conflict tracking and a retrieval-quality gate.
Local-first LanceDB vector memory with a strict write contract, calibrated abstention, typed relations, conflict tracking and a retrieval-quality gate. Requires local Ollama + nomic-embed-text.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install lancedb-suite
Said no? Turn it on later:
hermes plugins enable lancedb-suite
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).
Use the signed-in Aside browser as Hermes's browser when the Aside CLI is installed.
Good to know before installing
Runs the local aside CLI to drive your signed-in Aside browser (page text, screenshots, Aside memory, model-written JavaScript via aside_repl) without a Hermes approval prompt; Aside's permission level is a user-only setting (default ask) that covers aside_exec only. Optional pre_tool_call hook blocks Hermes' built-in browser tools while Aside is ready when browser_policy is always. Reads Aside's settings.json for the model list; 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 aside-browser
Said no? Turn it on later:
hermes plugins enable aside-browser
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).
Read-only memory.provider for GBrain (garrytan/gbrain, MIT; not affiliated). After each non-trivial turn it searches a GBrain MCP server (`gbrain serve --http`) in the background and injects up to the configured limit (3 by default, capped at 10) of `[source:slug] title` pointers into the next turn as fallible background context. It never writes to GBrain and adds no tools or hooks.
Good to know before installing
After each non-trivial turn, the first 500 characters of your message are sent to GBRAIN_MCP_URL (default http://127.0.0.1:3131/mcp; plain http to a non-loopback host is refused unless GBRAIN_POINTER_ALLOW_HTTP=1), and the profile's GBrain OAuth client id and secret go to that server's /token endpoint. Redirects and proxy settings are ignored. Only the slug, title and source id of up to 10 results are kept and injected into the next turn as background context; rows GBrain flags as suspected injection are skipped. Tokens and pointers stay in memory only. It never writes to GBrain; no other network calls, no telemetry.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs GBRAIN_MCP_CLIENT_ID, GBRAIN_MCP_CLIENT_SECRET), then asks whether to turn it on.
hermes plugins install gbrain-pointer
Said no? Turn it on later:
hermes plugins enable gbrain-pointer
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).
GitHub and GitHub Enterprise tools with bot-first attribution and approval-gated issue/PR writes.
Good to know before installing
Authenticates as a GitHub App from GITHUB_APP_ID, GITHUB_APP_INSTALLATION_ID and a private key in GITHUB_APP_PRIVATE_KEY or GITHUB_APP_PRIVATE_KEY_PATH/_FILE (read from the profile env or HERMES_HOME/.env, held in memory only, never written or logged), falling back to GITHUB_TOKEN/GH_TOKEN or `gh auth token` when no App variables are set, and reports which identity acted in every result. Talks only to https://api.github.com or the operator-configured GITHUB_API_URL / settings.api_url (HTTPS, no redirects; no tool argument can change the host). Issue/comment/review/merge writes stay disabled until settings.allow_write_actions is true and each one additionally goes through Hermes's human-approval prompt via its pre_tool_call hook (an 'always' answer does not persist).
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 github_app
Said no? Turn it on later:
hermes plugins enable github_app
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).
Community Zvec memory backend for Hermes Agent - in-process HNSW + RocksDB FTS store with native hybrid retrieval and session-safe lock governance; embeddings via any Ollama-compatible endpoint (local Ollama bge-m3 by default).
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install memory-zvec
Said no? Turn it on later:
hermes plugins enable memory-zvec
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).
Persistent memory for agents, shared across tools: save preferences, decisions and lessons and recall them later by natural-language search; rating a recalled memory as helpful or misleading re-ranks what comes back next; shared rooms (beta) let several people's agents work from one memory. Portable Agent Plugins v1 package (plugin.json + mcp.json + skills/) pointing at the hosted Mnemoverse MCP server (Streamable HTTP, OAuth 2.1 + DCR); the two bundled skills load under a namespaced name.
Good to know before installing
Hosted-only connector; Hermes runs no code from the package (scripts/ holds the repository's own CI checks). Every tool call goes to the vendor's remote MCP server at mcp.mnemoverse.com (authorization server auth.mnemoverse.com, browser sign-in on console.mnemoverse.com); memories the agent writes are stored in the signed-in user's Mnemoverse account, and recalled memories are pulled into the session context. OAuth tokens are held and refreshed by Hermes, never by the package. No telemetry, background process or self-update code.
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 mnemoverse
Said no? Turn it on later:
hermes plugins enable mnemoverse
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 memory and context compression for Hermes Agent with local SQLite or flat-file storage.
Good to know before installing
Replaces the memory provider (memory.provider: nachos) and, only when context.engine: nachos is set, the context engine; the provider injects a system-prompt block telling the agent to use the nachos_memory_* tools and keep built-in memory disabled; opt-in semantic ranking either runs a separately installed nachos-embeddings CLI or sends the turn query plus memory titles/summaries to api.openai.com with OPENAI_API_KEY; all storage is local under $HERMES_HOME/nachos/.
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 nachos
Said no? Turn it on later:
hermes plugins enable nachos
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).
Desktop-only, read-only monitor for pending memory and skill write approvals.
Good to know before installing
The pane's API reads pending/memory/*.json and pending/skills/*.json under the default Hermes root and every named profile directory beneath it (all profiles, not only the active one), and returns only counts, age buckets, oldest age, and per-item profile/subsystem/id/action/origin/created_at/age_seconds. It never returns or displays summaries, payloads, or record content; it exposes no approve, reject, or delete actions; it registers no tools, hooks, or middleware, performs no network I/O, and holds no credentials.
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 pending-queue-monitor
Said no? Turn it on later:
hermes plugins enable pending-queue-monitor
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).
Automatic recall sends the first 4,000 characters of each nontrivial local prompt to app.mypenny.ai as a search query, and the agent can save notes there through penny_remember without a Hermes approval prompt; works only in local CLI/TUI conversations (cron, subagents and gateways are refused); login is a manual command that registers its own OAuth client with clerk.mypenny.ai and briefly listens on 127.0.0.1 for the callback; tokens are kept in <HERMES_HOME>/penny/auth.json (owner-only) and are not removed on uninstall; no raw transcript upload, telemetry or other-client credential reuse.
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 penny
Said no? Turn it on later:
hermes plugins enable penny
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.
Cortexlayer
Community
CortexLayer memory provider — page-linked long-term memory with link-expansion retrieval, wired into Hermes' automatic per-turn recall (prefetch) and persistence (sync_turn), plus a pre-compress checkpoint so evidence…
CortexLayer memory provider — page-linked long-term memory with link-expansion retrieval, wired into Hermes' automatic per-turn recall (prefetch) and persistence (sync_turn), plus a pre-compress checkpoint so evidence Hermes' own context compaction would otherwise drop is saved first. Platform mode only: each turn's query and conversational content is sent to the hosted api.cortexlayer.net (HTTPS, API-key authenticated) for storage/retrieval — no local/offline mode. Requires a free CortexLayer account and API key.
How to install
Install it. Hermes asks for any API keys it needs (this one needs CORTEX_API_KEY), then asks whether to turn it on.
hermes plugins install cortexlayer
Said no? Turn it on later:
hermes plugins enable cortexlayer
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).
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 Arabic/English intelligent memory with canonical facts, conflict lifecycle, bounded recall, and selective Hermes cloud enrichment.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install intelligent_memory
Said no? Turn it on later:
hermes plugins enable intelligent_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.
Gbrain Retrieval Reflex
Community
pre_llm_call hook plugin, enabled with `hermes plugins enable`: injects ambient context from a GBrain instance before each turn (volunteer_context, then a hybrid-query fallback).
pre_llm_call hook plugin, enabled with `hermes plugins enable`: injects ambient context from a GBrain instance before each turn (volunteer_context, then a hybrid-query fallback). Not a `memory.provider`. Silent no-op when GBrain is unreachable or no token is set.
Good to know before installing
Before each non-trivial turn the last six user and assistant messages (truncated) and the current message are sent with a GBRAIN_TOKEN bearer token to GBRAIN_MCP_URL (default http://127.0.0.1:3131/mcp), and returned brain-page text is injected into the turn.
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 gbrain-retrieval-reflex
Said no? Turn it on later:
hermes plugins enable gbrain-retrieval-reflex
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.
Lightningai Rate Limit
Community
Per-process throttle for Lightning AI (https://lightning.ai/api/v1) keeping LLM requests within the ~15 requests/min limit, using an in-memory token bucket.
Per-process throttle for Lightning AI (https://lightning.ai/api/v1) keeping LLM requests within the ~15 requests/min limit, using an in-memory token bucket. Gates only calls whose provider or base_url points at Lightning AI; no-op otherwise.
Good to know before installing
Registers one llm_execution middleware and nothing else; no network calls, files, or processes of its 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 lightningai-rate-limit
Said no? Turn it on later:
hermes plugins enable lightningai-rate-limit
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).
Excel-backed hierarchical long-term memory tree (10-row cap per workbook, dynamic branching, leaf pointers). Classifier defaults to the host model; third-party keyless rotation is opt-in.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install excel_line
Said no? Turn it on later:
hermes plugins enable excel_line
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).
Agent Plugins v1 package: one skill plus one stdio MCP server (memory_select) started with uv run from the checkout. Needs uv on PATH. Registers no Hermes tools or hooks; do not expect jev_* tools.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install jev-memory-selector
Said no? Turn it on later:
hermes plugins enable jev-memory-selector
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).
Memobase memory provider — self-hosted user profile + event timeline recall, with hybrid BM25/vector/entity retrieval and automatic per-turn prefetch.
How to install
Install it. Hermes asks for any API keys it needs (this one needs MEMOBASE_API_KEY, MEMOBASE_BASE_URL), then asks whether to turn it on.
hermes plugins install memobase
Said no? Turn it on later:
hermes plugins enable memobase
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).
Metronix memory provider for Hermes with prefetch recall and built-in memory write-through.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install metronix
Said no? Turn it on later:
hermes plugins enable metronix
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-only YantrikDB dashboard for Hermes Agent memory operations
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install yantrikdb-hermes-dashboard
Said no? Turn it on later:
hermes plugins enable yantrikdb-hermes-dashboard
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).
Disclosure — copies .env key values (and opt-in auth.json backups) between profiles; rewrites other profiles' SOUL, memory and config.yaml.
Good to know before installing
Copies .env key values (and opt-in auth.json backups) between profiles; rewrites other profiles' SOUL, memory and config.yaml. Cross-profile config pane with copy+manifest reconcile and per-group scope.
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 profile-pane
Said no? Turn it on later:
hermes plugins enable profile-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.
Entropicmem
Community
Durable local memory for Hermes agents: SQLite FTS5 facts with cited, explainable recall; a Markdown vault with knowledge-graph export and an interactive visual graph.
Durable local memory for Hermes agents: SQLite FTS5 facts with cited, explainable recall; a Markdown vault with knowledge-graph export and an interactive visual graph; and turn-prefetch context injection with reason tokens. Write policy auto-redacts high-confidence secrets at write time (other PII types are warn-only findings) and stored-content injection screening flags and warns on recall and prefetch payloads (flag-and-warn, fail-open by design, not a blocking filter). Includes a 34-command CLI, destructive-op gates with automatic backups, and an append-only audit log.
Good to know before installing
All memory data (vault markdown, memory.db, index.db, backups) stays local under HERMES_HOME/entropicmem/; a shared publish DB defaults to HERMES_HOME/entropicmem-shared/. The CLI init command appends ENTROPICMEM_* settings to HERMES_HOME/.env (append-only). Vector embeddings are off by default; only with embeddings_enabled: true (provider) or ENTROPICMEM_EMBEDDINGS=1 / query --semantic (CLI) and the optional sentence-transformers extra installed does first use download all-MiniLM-L6-v2 weights from huggingface.co; otherwise the provider has no network egress. The CLI ingest command fetches a user-supplied URL; CLI graph export writes to ./export in the cwd by default and its HTML loads D3/marked from d3js.org and cdn.jsdelivr.net when opened; CLI graph serve starts a loopback HTTP server. entropicmem_patch_core edits the plugin's own Core-memory markdown (Persona/User_Profile), not Hermes core, and is 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 entropicmem
Said no? Turn it on later:
hermes plugins enable entropicmem
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).
Snapcompact context engine: archives conversation history as dense bitmap PNG frames that vision models read back at ~1/3 the token cost.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-snapcompact
Said no? Turn it on later:
hermes plugins enable hermes-snapcompact
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).
past.dev memory provider: recall before each turn from source-traced memory of past conversations, with sessions sent to past.dev when they end. Maintained by past.dev.
Good to know before installing
The user's message (as the recall query) and each session's user and assistant text, with common secret shapes redacted, are sent to the past.dev API (api.past.dev by default, or the address you configure) under your past project key, with a past-hermes/<version> User-Agent; the key and identity are read from PAST_API_KEY or ~/.past/config.json, which past.dev's other connectors share; off by default on messaging-gateway sessions.
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 pastdotdev
Said no? Turn it on later:
hermes plugins enable pastdotdev
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.
Severian
Community
Local-first long-term memory for Hermes agents: a canonical append-only store (SQLite or PostgreSQL+pgvector) with five-dimensional tenant/profile/collection/agent/session scope, hybrid BM25+vector retrieval…
Local-first long-term memory for Hermes agents: a canonical append-only store (SQLite or PostgreSQL+pgvector) with five-dimensional tenant/profile/collection/agent/session scope, hybrid BM25+vector retrieval with a re-ranker, memories that cite the observations they came from, per-turn user facts, real dates next to relative times, truth resolution when a newer fact replaces an older one, and a conflict note when two returned memories disagree. Fully offline by default; Qwen3-Embedding-0.6B semantic embeddings opt-in, locally or in a user-owned sidecar. On OmniMemEval's public long-term-memory leaderboard (its own models, prompts and full public sets) it scores 90.6 LongMemEval (1st), 87.3 LoCoMo (2nd) and 71.6 BEAM 100K (2nd, within noise of the lead); it re-ran LCM-X to check the board's records, and per-question results, a strict second marker and scripts are published in the repo.
Good to know before installing
Stores every conversation turn in one SQLite database under the Hermes root (`<hermes root>/severian`) shared by all profiles with rows scoped per profile, or in the PostgreSQL database named by `SEVERIAN_DSN`; the opt-in Qwen/Granite embeddings download a model from Hugging Face on first use, and the opt-in embedding sidecar sends memory text to the URL you configure.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs SEVERIAN_DSN), then asks whether to turn it on.
hermes plugins install severian
Said no? Turn it on later:
hermes plugins enable severian
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.
Plugin Catalog (Italian)
Community
The official Hermes plugin catalog in a native page (sidebar entry, route /catalogo, plus a command-palette entry) with an Italian interface and on-the-fly Italian descriptions: Google Translate first, MyMemory…
The official Hermes plugin catalog in a native page (sidebar entry, route /catalogo, plus a command-palette entry) with an Italian interface and on-the-fly Italian descriptions: Google Translate first, MyMemory as a second public source, and a final fallback to the user's own local llama.cpp model.
Good to know before installing
It fetches the public catalog feed (hermes-agent.nousresearch.com) and, when you open a plugin entry, sends that entry's English description to translate.googleapis.com (Google Translate's keyless public endpoint) and, if that fails, to api.mymemory.translated.net; nothing else leaves the machine. It reads no credentials or Hermes files, and its backend route is empty. Translation runs when a plugin entry is opened, not for the whole catalog. No telemetry. UI is Italian-first with an English bundle.
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 catalogo-it
Said no? Turn it on later:
hermes plugins enable catalogo-it
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 Windows Tasks
Community
Answer "what does this machine run on its own, and did it work" on Windows: win_scheduled_tasks lists the Task Scheduler's tasks with their state (Ready, Running, Disabled), the account each runs as, its first…
Answer "what does this machine run on its own, and did it work" on Windows: win_scheduled_tasks lists the Task Scheduler's tasks with their state (Ready, Running, Disabled), the account each runs as, its first action's command line, its triggers in words (at logon, daily, weekly, at a time, on event), its last and next run with the machine's offset, its missed runs, and what its last result code means - 0x80070002 is a program that is no longer there, 0x800710E0 a task that needed a desktop it did not have, 0x40010004 one that was stopped, 0x80040154 a COM class that is not registered. win_scheduled_task_detail takes one task and gives its triggers with start boundaries and repetition, its actions with arguments and working directory, its principal and the settings that decide whether it runs on battery or when late; a task with no triggers but MaintenanceSettings runs during automatic maintenance and the notes say so rather than leaving an empty list. Use it for why a logon task keeps failing, for finding what an uninstalled program left behind at logon, for telling a disabled task from a broken one, and for reading a task's command line before trusting it. Read-only: nothing is created, started, changed or deleted. Reads through the ScheduledTasks cmdlets rather than the store on disk, because the TaskCache registry tree and C:\Windows\System32\Tasks both answer access denied without elevation, and rather than schtasks /Query /FO CSV, which is localized and interleaves error lines for tasks whose definitions are gone. The plugin declares no Python dependencies; there is no network call and no file write. Windows only.
Good to know before installing
The tools report task paths, command lines, working directories, account names and SIDs to the model, and those reveal what the person has installed, what starts at their logon, and the paths under C:\Users\<name>; treat the output like a Task Scheduler window opened on their 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 hermes-windows-tasks
Said no? Turn it on later:
hermes plugins enable hermes-windows-tasks
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).
Memory provider with keyed corrections you can undo. A correction retires the old value by key, so it stops being recalled, and inspeximus_revert puts the previous value back from the key alone, without anyone retyping what the record used to say. Recall before each turn returns retrieval minus what a later correction retired, so a value corrected three sessions ago cannot come back as context. Adds inspeximus_remember, inspeximus_correct, inspeximus_revert, inspeximus_forget and inspeximus_forget_me.
Good to know before installing
Installs the inspeximus package from PyPI (inspeximus>=3.23.1,<4, including its `inspeximus` command-line tools) into the Hermes environment; the provider makes no network calls and carries no telemetry: memories live in a local JSON file under the profile's Hermes home (or a path you set), recalled memories are added to each turn's context and to the compression summary prompt, and writes made with the built-in memory tool are mirrored into the store.
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 inspeximus
Said no? Turn it on later:
hermes plugins enable inspeximus
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.
Perf HUD
Community
Live performance HUD for Hermes Desktop: a status-bar chip with core-compatible TPS (sum of output tokens over sum of API durations for the last 10 completed calls, the same window and arithmetic as Hermes' own…
Live performance HUD for Hermes Desktop: a status-bar chip with core-compatible TPS (sum of output tokens over sum of API durations for the last 10 completed calls, the same window and arithmetic as Hermes' own status bar) in `tps`, `tps_ttft` or `calls` form, and a statistics popover with TPS, a separately labelled Session Avg TPS (the same ratio over every call in the session), median TTFT from `first_chunk_at`, LLM calls, an `Agent steps*` compatibility alias (equal to LLM calls, footnoted inside the snapshot by `agent_steps_note`), turns, errors, input, output and cache-read tokens, cache hit rate on Hermes' `cache_read / (cache_read + input)` buckets, tool calls and tool time, tool time share, wall-clock session duration, and the model and provider. Two controls — Reset current statistics (clears the plugin's own in-memory counters, never Hermes session state) and Clear history — plus local performance history for the last 50 sessions. Observes only: nine observer hooks, no tool or message is ever blocked, rewritten or reordered, no Hermes core file is touched, the aggregation layer is pure with no I/O and no host imports, all handlers are fail-open so a telemetry bug cannot break a turn, and a corrupt history file is quarantined instead of raised.
Good to know before installing
Reads only from the observer payloads: token usage buckets (input, output, cache read, cache write, reasoning), API and tool timings, first-chunk timestamps, model and provider names, session ids, and tool names plus error status for the counts; prompts, model responses, conversation contents, tool arguments and tool results are never read and have no field in its snapshot, its desktop event or its history record. Writes exactly one JSON file per profile at `<HERMES_HOME>/plugin-data/agent-plugin-perf-hud-*/history.json` containing only session_id, model, provider, started_at, updated_at, duration_ms, ttft_ms, tps_core, input_tokens, output_tokens, cache_hit_pct, tool_time_ms and llm_calls, allow-list enforced, atomic, capped at 50 sessions; no other disk writes, and no config change beyond the documented `plugins.entries.perf-hud.settings.*` keys (chip_enabled, chip_metric, history_enabled, history_max_sessions, poll_ms, broadcast_min_interval_ms). Desktop updates travel over Hermes' in-process plugin event bridge (`broadcast_plugin_event`, topic `plugin.perf-hud.stats.update`, throttled to 400 ms) and its REST routes are served by the user's own local dashboard at /api/plugins/pe
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 perf-hud
Said no? Turn it on later:
hermes plugins enable perf-hud
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.
Session Relay
Community
Hands a long-running conversation over to a fresh session before the context window fills up: a ⚡ chip in the status bar shows live context usage, and at the threshold (45% by default) the agent writes a…
Hands a long-running conversation over to a fresh session before the context window fills up: a ⚡ chip in the status bar shows live context usage, and at the threshold (45% by default) the agent writes a hand-off note while the plugin opens a new chat, seeded with that note as its first message and named after the current one (+1). On Telegram and other messaging platforms the gateway half provides a session_relay_handoff tool; after /new it attaches that chat's note to the first message of the new session, so the fresh session opens with the hand-off.
Good to know before installing
Each relay runs one extra agent turn and therefore uses model tokens.
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 session-relay
Said no? Turn it on later:
hermes plugins enable session-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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
You should know
Community
A side agent rereads the conversation while Hermes works on longer turns and surfaces the one thing you might have missed — a silent tradeoff, an unverified result, an irreversible action — as a dismissible…
A side agent rereads the conversation while Hermes works on longer turns and surfaces the one thing you might have missed — a silent tradeoff, an unverified result, an irreversible action — as a dismissible note above the prompt.
Good to know before installing
On tool-using turns in Desktop, CLI and TUI (configurable via `platforms`), sends up to 12,000 characters of the recent conversation, including clipped tool calls and results, to Hermes's configured auxiliary model up to five extra times per turn (45 s cooldown), which adds model cost; notes are stored in the plugin's own data folder.
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 you-should-know
Said no? Turn it on later:
hermes plugins enable you-should-know
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.
