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.
100 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.
Senler.io
Community
Get task-specific guidance for Senler agents, automations and knowledge, connect your account through MCP OAuth, and automate selected webhook events with an outbound Relay connection.
Get task-specific guidance for Senler agents, automations and knowledge, connect your account through MCP OAuth, and automate selected webhook events with an outbound Relay connection.
Good to know before installing
Hermes installs the declared `python-socks[asyncio]` dependency for native SOCKS proxy support. First activation of the enabled plugin adds a `senler-io-user` MCP server (mcp-senler-io-user.senler.io; OAuth handled by Hermes) to the profile's config.yaml and records completion through plugin settings, which native uninstall clears. Reinstalling and enabling the plugin prepares a missing MCP again. The old durable marker from 0.5.2–0.5.3 is ignored, so upgrading restores a missing entry once, including an entry manually removed before this upgrade. Existing compatible and disabled connections are preserved; later loads in the same installation respect manual removal. Explicit chat setup can restore a removed connection. Relay setup enables a `senler-io` gateway platform in the same profile. Once you enable automation, the gateway keeps an outbound WSS connection to a Senler-supplied Relay address and runs unattended agent turns on incoming Senler events (customer messages, leads, etc.); the platform is `trusted_inbound`, so these events bypass Hermes allowlists and pairing, and customer text reaches the model as untrusted data. During those runs a hook allows the Senler MCP and nati
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 senler-io-user
Said no? Turn it on later:
hermes plugins enable senler-io-user
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.
Morning Briefing
Community
Personal daily newspaper for Hermes: gathers weather, calendar, AQI, curated 36-hour news (timestamped Reddit RSS + X + web search, per-story QR codes), and newsletter digests, renders one 8.5x11 newsprint page, and…
Personal daily newspaper for Hermes: gathers weather, calendar, AQI, curated 36-hour news (timestamped Reddit RSS + X + web search, per-story QR codes), and newsletter digests, renders one 8.5x11 newsprint page, and prints it every morning via a cron job.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install morning-briefing
Said no? Turn it on later:
hermes plugins enable morning-briefing
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 Muse
Community
A proactive companion for Hermes: follows accepted goals (active/done/cancelled), prepares sourced research and Feed articles, maintains memory, and assembles rolling 30-day or natural-month calendar views.
A proactive companion for Hermes: follows accepted goals (active/done/cancelled), prepares sourced research and Feed articles, maintains memory, and assembles rolling 30-day or natural-month calendar views. Read-only local Dashboard/Desktop pages show Feed, Ideas and Goals; profile selection cannot install, enable or disable Muse in any profile. One Skill, one state tool and six fixed recurring jobs; selected notices and weekly/monthly reports go to the active profile's Bot Chat and run an assistant turn there. Sources, authorization, quiet hours and actual result/delivery receipts remain distinct; partial coverage is not global availability.
Good to know before installing
First load creates profile-local files/SQLite state and owned Cron scripts/jobs. Private/local input inbox rows retain their first 8000 characters and source identities, with associated chat/user routing IDs when present. The newest 500 remain; older rows are cleaned on later input only after both hourly/nightly cursors cover them. Unprocessed backlog can exceed 500 and has no fixed retention time. Native conversations/tool results are read separately; research records can retain returned payloads. Idempotency journals and oversized tool results stay in the profile state database without automatic expiry and may contain written content or tool output. Bounded conversation previews support full revision-checked paging. Delegates are instructed to remain read-only under inherited permissions, not sandboxed. Workers always use public delegate_task dispatch and follow the user's delegation settings; leave delegation.provider/model empty to keep the parent model. New Cron watches require cron.allow_agent_scheduling; local goal registration creates no job. Watch prompt/stop fields each allow 4000 characters; new repeating watches (interval or cron) must be at least 30 minutes apart, one-
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-muse
Said no? Turn it on later:
hermes plugins enable hermes-muse
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.
Job Search
Community
A private, local-first job-search assistant that finds postings, judges them against your prose preferences (no scores), and writes digests on a schedule you control.
A private, local-first job-search assistant that finds postings, judges them against your prose preferences (no scores), and writes digests on a schedule you control.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install job-search
Said no? Turn it on later:
hermes plugins enable job-search
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).
Inspect captured browser verification evidence locally when an agent task is interrupted by a CAPTCHA. Portable Agent Plugins v1 package (pinned stateless mcp.json + skill); needs Node.js 22.19+/24.11+/26+ with npx on PATH.
Good to know before installing
On first start Hermes runs `npx rea-captcha@0.3.1`, which downloads that exact npm package and its dependencies (incl. Playwright) from the npm registry; the catalog config is stateless, so only the read-only, local captcha_analyze works and the browser-session tools fail closed until you configure a separate stateful server; no telemetry, hosted solver, browser-profile copying, or cookie/token transfer.
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 rea-captcha
Said no? Turn it on later:
hermes plugins enable rea-captcha
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.
Usage Guard
Community
Keeps an agent inside its subscription allowance: refuses a provider dispatch once a subscription usage window is exhausted, so an account that allows paid extra usage stops at the wall instead of spending overage.
Keeps an agent inside its subscription allowance: refuses a provider dispatch once a subscription usage window is exhausted, so an account that allows paid extra usage stops at the wall instead of spending overage. Reads the usage Hermes already displays, holds no credentials, and never touches account or billing settings.
Good to know before installing
Refuses main-loop provider calls (including MoA turns) for the providers in `provider_keys` (Anthropic and OpenAI Codex by default) when a subscription usage window reaches `threshold_percent`, and by default (`fail_open: false`) also refuses when usage data is missing, stale, unreadable, or the guard's own config is malformed; usage is read through Hermes's own account-usage fetcher (no credentials held, at most one read per source every 180 seconds by default) and cached in $HERMES_HOME/plugin-data/usage-guard/usage.json; a `pre_llm_call` hook adds a short usage note to the next turn's context at 80% and 90% used by default, and an opt-in (off by default) `llm_request` middleware lowers an existing output-token budget near the usage limit; both read only the cache, never the network; auxiliary calls (compression, vision, titles, MoA advisors) are not gated.
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 usage-guard
Said no? Turn it on later:
hermes plugins enable usage-guard
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).
Per-call delegation across your own subscriptions. The model sends each subagent to a named route with delegate_to(route, goal, context); each route pins a provider Hermes already knows (Claude, Codex or Antigravity subscription plugins, ACP provider plugins) and a model. delegate_task, by contrast, uses the one target in config.yaml. Subagents launch through ctx.subagent_lifecycle. A child counts as out of quota only on an unambiguous provider error or a measured window at 100 %, and the route never switches on its own: a policy decides whether the parent asks you, picks another route, or waits.
Good to know before installing
A pre_tool_call hook blocks delegate_task spawns while routes are configured (list/steer/stop pass); an api_request_error hook records quota errors in memory. Quota is read with Hermes' fetch_account_usage (Anthropic and OpenAI Codex) on /ohx quota and after a provider error. No other network egress, no files 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 orquehelx
Said no? Turn it on later:
hermes plugins enable orquehelx
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 OSINT Map
Community
A live situational-awareness globe in Hermes Desktop: earthquakes (USGS), disaster alerts (GDACS), natural events (NASA EONET), US severe weather (NWS), military and nearby aircraft (adsb.lol), satellites propagated…
A live situational-awareness globe in Hermes Desktop: earthquakes (USGS), disaster alerts (GDACS), natural events (NASA EONET), US severe weather (NWS), military and nearby aircraft (adsb.lol), satellites propagated live from CelesTrak elements, GDELT news incidents, official traffic cameras (Transport for London, Singapore LTA) and shipping chokepoints on a dithered 3D globe, with satellite orbits, aircraft tracks and live camera stills, country dossiers (World Bank facts, events, headlines), NOAA space weather, markets, a feed of events, headlines and alerts, and a passive recon toolkit (DNS, RDAP, TLS, security headers, CT subdomains, CVE with CISA KEV, IP, GitHub, MAC). Five agent tools (osint_situation, osint_events, osint_country, osint_recon, osint_news) answer from the same sources in any chat, and the page's Brief me, Ask Hermes and dossier buttons open a chat that uses them. No keys needed; an optional TWELVEDATA_API_KEY (plugin setting, read through Hermes's secret scope) adds equities and commodities. Unofficial; not affiliated with any data provider.
Good to know before installing
The gateway fetches public data from fixed hosts (earthquake.usgs.gov, eonet.gsfc.nasa.gov, gdacs.org, api.weather.gov, data.gdeltproject.org, api.adsb.lol, celestrak.org, services.swpc.noaa.gov, api.tfl.gov.uk and api.data.gov.sg (camera lists), and camera stills from TfL's JamCams bucket on s3-eu-west-1.amazonaws.com and images.data.gov.sg, fetched only by camera id for a camera the user opens, api.worldbank.org, the BBC, Al Jazeera, DW, Guardian and France 24 RSS feeds, api.coingecko.com, and api.twelvedata.com with the key in a header when set), cached and only while the page is open or a tool is called, with a hermes-osint-map User-Agent; recon sends the domain, IP, CVE id, GitHub name or MAC prefix the user or agent enters to dns.google, rdap.org, crt.sh, cve.circl.lu, cisa.gov, ipwho.is, api.github.com and api.macvendors.com, and the TLS and headers lookups connect directly to the host named, refusing private, loopback, link-local, CGNAT and other internal addresses on every redirect, on ports 443/8443 (TLS) and 80/443/8080/8443 (headers) only; GDELT incidents are machine-coded from news coverage and labelled as such; the page keeps its layer choices in Desktop plugin storag
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-osint-map
Said no? Turn it on later:
hermes plugins enable hermes-osint-map
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.
Workflow Record
Community
hermes record: demonstrate a browser workflow once (clicks, field values, navigations) and its bundled skill lets /learn turn the recording into a skill that replays it with the browser tools.
hermes record: demonstrate a browser workflow once (clicks, field values, navigations) and its bundled skill lets /learn turn the recording into a skill that replays it with the browser tools. A Hermes Labs plugin: built by Nous Research, not supported.
Good to know before installing
Attaches over CDP to a Chromium you point it at (--cdp, BROWSER_CDP_URL, browser.cdp_url or 127.0.0.1:9222) and records what you do in that tab until Ctrl-C; password, one-time-code and card fields are masked inside the page as {SECRET:name} and never written. Recordings stay local in <HERMES_HOME>/recordings; nothing is sent anywhere until you run /learn on one, which hands it to your active model.
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 workflow-record
Said no? Turn it on later:
hermes plugins enable workflow-record
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).
A live board your agent builds for you: tabs of notes, tables, charts, KPI cards and live Hermes data, in the dashboard and Hermes Desktop. It appears as a Board tab in the dashboard and a page in Desktop, and the agent lays it out with 19 native boardstate_* tools, approval widgets included. Runs a local Node >= 20 sidecar on loopback with a per-spawn nonce; no network access unless you opt in to operator-gated connectors.
Good to know before installing
Spawns a local Node.js ≥20 sidecar (from PATH/HERMES_NODE_BIN, nothing downloaded) on 127.0.0.1 on first use; state under HERMES_HOME/boardstate-state/. Reads the dashboard's loopback session token from Hermes internals (web_server._SESSION_TOKEN) and passes it to the sidecar for live usage/sessions/cron widgets; mounts one token-gated static route for approved widget assets. No outbound network unless you author boardstate.connectors.json (stdio/HTTP MCP connectors); connector actions need operator approval. Ships one plugin skill, boardstate:boardstate-report-problem, which drafts a bug report and files it with the GitHub CLI only after the user approves the exact text.
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 boardstate
Said no? Turn it on later:
hermes plugins enable boardstate
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.
ActVox
Community
Make Hermes a team member in an ActVox workspace: on a schedule it works the tasks people assign it and answers the comments that @mention it, and submits each task for a person's review.
Make Hermes a team member in an ActVox workspace: on a schedule it works the tasks people assign it and answers the comments that @mention it, and submits each task for a person's review. Skills actvox:actvox and actvox:actvox-inbox, a first-turn inbox line (pre_llm_call), /actvox inbox|status, and hermes actvox setup|install-gate. A cron pre-run gate wakes the agent only when the inbox has work, so an empty tick makes no model call.
Good to know before installing
ActVox is reached only through the user's own actvox MCP server (ctx.call_mcp, needs plugins.entries.actvox.mcp_allowlist) and the user's own actvox CLI (the gate runs `actvox inbox --all --json`); on the first turn of every non-cron session the pre_llm_call hook calls the server's check_inbox (up to 5 s) and adds one line saying how many tasks and mentions wait; the plugin holds and reads no credential and sends no telemetry. `hermes actvox install-gate` writes one file, $HERMES_HOME/scripts/actvox-inbox-gate.py, only on that explicit command and never over a file it did not write; gate state lives in $HERMES_HOME/plugin-data/actvox/. No background work of its own: the cron job runs only after the user creates it, and from then on anyone who can assign Hermes a task or @mention it in your ActVox workspaces decides what an unattended agent run on your host works on, with that job's toolsets (dangerous commands follow approvals.cron_mode, deny by default). Unattended writes need the default trust: full on the actvox server.
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 actvox
Said no? Turn it on later:
hermes plugins enable actvox
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).
Give your agent a team: named subagents with their own instructions, tools and model, which it assigns work to, checks on and steers mid-task. The operator defines the roster; the agent follows up with a digest of earlier results and can work a Kanban teammates lane with a review handoff. Launches subagents only through the public ctx.subagent_lifecycle API. Stock Hermes; no patched core.
Good to know before installing
Adds six tools (teammates_roster, teammate_assign, teammate_check, teammate_wait, teammate_message, teammate_stop) and a /teammates command; the model picks only a teammate name, and the operator's config decides what it means. Teammates run as in-process Hermes subagents using credentials selected by Hermes from the parent, delegation settings or an operator-configured teammate route where supported. Toolsets narrow the parent's tools at toolset granularity only (the file toolset includes write_file and patch); Hermes can add inherited MCP toolsets back unless delegation.inherit_mcp_toolsets is false. A teammate with invalid settings refuses to launch. A delegated child cannot start teammates. Steering uses the lifecycle steer where Hermes provides it, otherwise delegate_task's steer action with the turn-bound parent. Under plugins.isolation: host every tool except the roster refuses. Optionally the roster is read from an operator-named YAML file (roster_file, relative to the profile home or absolute, so several profiles can share one); the plugin never writes it. It keeps a per-profile SQLite run ledger in its plugin-data folder (goals, statuses, clipped summaries, role hashes an
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-teammates
Said no? Turn it on later:
hermes plugins enable hermes-teammates
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).
A Miro-like board the agent draws with its own tools and you edit in a desktop pane, both sides working on one JSON document. board_apply builds a whole diagram in one call from ordered ops (nodes, edges, free lines, groups, notes, captions, layered auto-layout, bus trunks); board_render writes a PNG for chat or the interactive HTML editor; board_watch reports your own pane edits back to the agent. The pane docks beside the conversation with the same editor, saves your edits, and takes agent updates live.
Good to know before installing
Board_render shells out to a headless Chrome/Chromium already on PATH (nothing is downloaded; private temp profile, sandbox kept unless running as root) for PNG and self-test rendering; boards live in ~/.hermes/board/ shared across profiles (HERMES_BOARD_DIR / HERMES_BOARD_RENDER_DIR / HERMES_BOARD_WATCH override); serves /api/plugins/hermes-board/ on the plugin host; reads this profile's state.db read-only to find the session board_watch should wake; no external network calls and no stored credentials; board_watch's wake into a messaging chat additionally needs plugins.entries.hermes-board.allow_gateway_injection: 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 hermes-board
Said no? Turn it on later:
hermes plugins enable hermes-board
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).
Rich, evidence-backed answer cards — tables, charts, metrics, timelines, sources — rendered inline in the desktop transcript
Good to know before installing
Image and ImageGallery cards load agent-supplied https image URLs (up to 8 per gallery) from any host when the card renders in Desktop
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-rich-ui
Said no? Turn it on later:
hermes plugins enable hermes-rich-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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Bot Forge
Community
Say "make me a <role>" and your agent spawns a complete Bot Mode Bot — name, face, SOUL.md, memory, tools, skills, routines, gateway — tested, with rollback.
Say "make me a <role>" and your agent spawns a complete Bot Mode Bot — name, face, SOUL.md, memory, tools, skills, routines, gateway — tested, with rollback. Then hire a whole crew in one call, ask what is waiting on you, and edit, teach, share and health-check Bots by chatting.
Good to know before installing
Spawns the hermes CLI to create and run Bot profiles under HERMES_HOME/profiles/, and installs its own small companion hook plugin (bot-forge-marks, two hooks, no tools) into each Bot profile it manages, enabling it in that profile's config.yaml; never the root profile. Disclosure — when a Bot journals a blocked/failed entry, the plugin emails its title and summary to your own address via the SMTP account in Hermes' EMAIL_* settings (TLS verified; off with notify_blocked or notify_email false); adopt_bots (off by default) installs the companion hook into every profile on load.
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 bot-forge
Said no? Turn it on later:
hermes plugins enable bot-forge
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.
Inbox
Community
hermes inbox: one read-only view of everything in flight for the active profile: failed or paused cron jobs, stalled or dropped delegations, orphaned background processes, blocked kanban tasks, running work…
hermes inbox: one read-only view of everything in flight for the active profile: failed or paused cron jobs, stalled or dropped delegations, orphaned background processes, blocked kanban tasks, running work, undelivered delegation results, upcoming cron runs and open chat sessions, with --json for scripts. A Hermes Labs plugin: built by Nous Research, not supported.
Good to know before installing
Reads processes.json, cron/jobs.json, runtime/active_sessions.json and state.db (SQLite read-only) in the profile's home, plus the shared kanban board's kanban.db (read-only); it never writes, repairs or prunes them, adds no model tools or hooks, and sends nothing anywhere.
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 inbox
Said no? Turn it on later:
hermes plugins enable inbox
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).
Render a chart inline in the Hermes Desktop transcript: the model emits ::echarts{labels=... values=...} and the plugin mounts an interactive SVG chart (dataZoom slider, click-to-filter legend, resize-aware, 280-560px height clamp) in the plugin SDK's transcript-directive slot.
Good to know before installing
No network calls, no shell commands, no stored credentials, no environment variables, no background processes, and nothing read or written outside the message it renders; the chart is drawn locally as inline SVG with no third-party libraries.
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 echarts-in-chat
Said no? Turn it on later:
hermes plugins enable echarts-in-chat
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.
Telegram Dashboard
Community
One pinned Telegram message with the state of your Hermes on one phone screen: gateway, backup, config drift, the cron ticker and its jobs, whether the Telegram channel is deaf, whether the agent sees its rules and…
One pinned Telegram message with the state of your Hermes on one phone screen: gateway, backup, config drift, the cron ticker and its jobs, whether the Telegram channel is deaf, whether the agent sees its rules and whether its memory writes stand unapproved, account limits and version. Read-only, no LLM calls, nothing to press.
Good to know before installing
Claude and Codex limits come from Hermes' own account-usage fetcher, called every tick (which, like /usage, may refresh OAuth tokens through Hermes' own auth code); at most once per limits_refresh_seconds (default 900 s) the Grok weekly pool is read from https://cli-chat-proxy.grok.com/v1/billing and /v1/settings with the xai-oauth token Hermes resolves (which, like any Hermes request to xAI, may refresh that OAuth token and save it to auth.json, or clear a dead one, through Hermes' own auth code), sending the header x-xai-token-auth xai-grok-cli that identifies the request as the Grok CLI (an undocumented xAI host Hermes itself does not use), and Kimi Code windows from the kimi-coding base URL /v1/usages with the kimi-coding key Hermes resolves (which, like any Hermes key lookup without a usable key in .env or the environment, may save Hermes' credential pool back to auth.json once when loading it changes something, e.g. a placeholder key in .env) and a User-Agent of claude-code/0.1.0 (undocumented provider surfaces), and up to four operator-configured limits_sources, if set, each with one GET to http on loopback only (127.0.0.1, localhost or ::1), with no proxy and no redirect, o
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 telegram_dashboard_probe
Said no? Turn it on later:
hermes plugins enable telegram_dashboard_probe
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).
Find people and coordinate real-world work through the RentAHuman marketplace.
Good to know before installing
Runs the third-party `rentahuman-mcp` server via npx, which sends your requests and your RentAHuman API key to rentahuman.ai and stores agent identity keys in `~/.rentahuman-identities/`; its tools can post and fund tasks, accept workers, send messages and release real money to people — write-capable calls ask for approval because the server is marked `trust: untrusted`, but each approval moves money or commits you to work.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs RENTAHUMAN_API_KEY), then asks whether to turn it on.
hermes plugins install rentahuman
Said no? Turn it on later:
hermes plugins enable rentahuman
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).
Topic-aware session title tracking for Hermes Agent. Hermes generates the first title by default; AutoTitler follows conversation changes and session close without changing the host title-generation switch.
Good to know before installing
Sends excerpts of each conversation (sampled user turns, short assistant replies, compaction summaries) to your Hermes title-generation model in the background, also for up to 200 recent untitled sessions at startup; needs plugins.entries.hermes-auto-titler.llm.allow_task_override (or allow_provider/model_override for a custom route). 0.3 no longer edits config.yaml, but users upgrading from 0.2.x keep auxiliary.title_generation.enabled=false until they re-enable it (/autotitler status shows the fix).
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-auto-titler
Said no? Turn it on later:
hermes plugins enable hermes-auto-titler
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).
Your agent follows up on its own: timed check-ins, recurring checks and watchers that wake it in the same chat when something changes. You (with /pulse) or your agent (with the pulse tool) arm follow-ups at a time, recurring checks, a check-in after a long silence, or deterministic watchers on a file, process, URL, read-only command or Hermes event (kanban, subagent, API error, reactions). A wake is a turn in the same messaging DM that armed it, on that chat's own model: no side model, cron session or subagent. Watchers decide without a model call; the agent answers each wake with a structured verdict (notify or stay silent, never a typed sentinel); a no-op governor slows, then pauses pointless wakes and asks once. Every guardrail is a user setting (quiet hours, daily caps, unanswered mute, floors, lifetimes) that the agent works inside and can never widen. A one-time reminder you ask for in chat bypasses the unanswered mute and daily caps; HeartBeat 2.0 grants that only in a turn that carries your message. Arming returns a one-line receipt saying when the wake will really fire, and a wake that could never fire before it expires is refused. It delivers to messaging-gateway DMs only and needs plugins.entries.heartbeat2.allow_gateway_injection: true. Ships the plugin skill `heartbeat2:heartbeat2-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
Wakes and watchers run full turns on the conversation's own model, billed like any message, at your conversation's context size, with the conversation's normal tools and approval prompts; the agent can arm wakes and watchers itself unless you set agent_can_create to ask_first or no; command watchers run allowlisted read-only commands (default gh pr view/checks, gh run view/list, git ls-remote/status/log) without an approval prompt, with no shell, a sanitized environment (no provider keys, GH_TOKEN or GITHUB_TOKEN) and the process group killed after 30 s, can use your stored git/gh credentials, and `git ls-remote <url>` / `gh -R` can contact any host your machine can reach; URL watchers make the GET requests you or the agent configured, without URL credentials, cookies, auth headers or proxies, always refuse cloud-metadata addresses and refuse private or local addresses unless url_allow_private is on; file watchers refuse paths Hermes blocks from reading; notes, summaries and event payloads are stored in plaintext in the profile's plugin-data; 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 heartbeat2
Said no? Turn it on later:
hermes plugins enable heartbeat2
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.
Omh
Community
Oh My Hermes (OMH) bridge: routing hints and role context for OMH workflow skills, per-task delegation model routing, plan todos and a status tool, a Hermes Desktop status pane (off until enabled), bounded evidence…
Oh My Hermes (OMH) bridge: routing hints and role context for OMH workflow skills, per-task delegation model routing, plan todos and a status tool, a Hermes Desktop status pane (off until enabled), bounded evidence probes that keep prepared work apart from observed results, and a file-backed memory provider.
Good to know before installing
Omh_delegate_route writes delegation.model/provider/reasoning_effort in $HERMES_HOME/config.yaml and the session hooks restore them; omh_gather_evidence runs allowlisted checks (python -m unittest with reporting flags only, python -m compileall, git diff --check, omh doctor/probe/docs/release checks) via subprocess on the host, outside any sandboxed terminal backend and without Hermes' terminal approval, in the agent working directory or below it, so it runs whatever test code that directory holds; omh_team (only with the separate OMH core package installed) asks once through the Hermes approval prompt for an exact list of up to 8 check commands from an accepted plan, then runs them on the host as each helper returns; omh_jev_ask posts model-supplied state and questions to api.typesafe.ai (openrouter.ai only when the operator opts in via ~/.omh/jev/settings.json) with the user's own TYPESAFE_API_KEY or OPENROUTER_API_KEY, only in a turn where the user names Jev; opt-in egress_attempts (re-registers chosen core tools, needs the operator's tool-override grant) and browser_adapter (vetoes core browser_* tools) settings; reads session and cost metadata from state.db read-only; state li
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 omh
Said no? Turn it on later:
hermes plugins enable omh
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.
Diaktoros
Community
Unattended GitHub pull-request review between two Hermes agents: one pushes fixes, a different one reviews, rounds are capped in verdicts, a watchdog reports silent stalls, and the loop never merges.
Unattended GitHub pull-request review between two Hermes agents: one pushes fixes, a different one reviews, rounds are capped in verdicts, a watchdog reports silent stalls, and the loop never merges.
Good to know before installing
Runs unattended Hermes agent turns inside bubblewrap (terminal and file tools, no network, no credentials); a host-side broker and the CLI write to GitHub (reviews, comments, labels, issues, repo webhooks, and opt-in fixer pushes, which may push CI fixes, merge commits of the base into a PR's own branch to resolve conflicts, and issue-fix branches and PRs, including an opt-in auto-fix that hands issues its triage seat labels (never P0-P2, capped per day) to the fixer without a maintainer, plus an opt-in clean merge of the base into a review-only author's same-repository PR branch when it conflicts or falls behind, a branch the loop does not own; it never merges a PR) with repo-scope PAT files you provide; edits Hermes's webhook_subscriptions.json directly and its watchdog re-adds this loop's routes while armed; writes gate scripts into the seat profiles' scripts/ folders and creates one hermes cron job (its migrate command replaces the old hermes-review-loop job and copies that plugin's settings); its backup command writes a 0600 archive of the plugin's state, including webhook route secrets, to a path you choose, and restore writes one back into the Hermes home and recreates the c
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 diaktoros
Said no? Turn it on later:
hermes plugins enable diaktoros
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 Cron
Community
Operating skill for Hermes cron: lifecycle rules (pause vs disable vs remove, `in 30m` vs `30m`), four ways to avoid needless LLM runs (no_agent, wakeAgent pre-check, monitor, [SILENT]), verify-after-change, a layered…
Operating skill for Hermes cron: lifecycle rules (pause vs disable vs remove, `in 30m` vs `30m`), four ways to avoid needless LLM runs (no_agent, wakeAgent pre-check, monitor, [SILENT]), verify-after-change, a layered runbook and a read-only doctor that complements `hermes cron doctor` and reports one error across several jobs as one scheduler fault and a cron store that cannot be written. Portable Agent Plugins v1 package (plugin.json + skills/); no tools, hooks, middleware or env vars.
Good to know before installing
Skill only, no network; the bundled doctor reads ~/.hermes/cron/jobs.json, ticker stamps and executions.db (or a named profile's store with --profile) read-only, checks the cron directory's permissions and free space without writing, and runs the local hermes cron doctor (argument list, no shell), whose job loader may repair malformed jobs.json entries (--no-builtin skips it).
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-cron
Said no? Turn it on later:
hermes plugins enable hermes-cron
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-driving multi-agent development team. Role-based workers (architect, developer, reviewer, tester, researcher, writer, devops) are each a real Hermes profile with its own SOUL.md and skills; they discuss and vote on decisions, and the adopted conclusion is executed by the same team. A "leader" profile chairs the discussions and a heartbeat cron wakes it to assess state, unblock workers and plan the next phase. Discussion and execution share one board: a motion is a sub-task of a per-project team channel task, speech and votes are `[agora:msg]` comments, the conclusion is written to task.result, and an adopted conclusion becomes execution tasks parented to the motion so context reaches workers through Hermes' own parent handoff. Ships 20 tools, 3 kanban lifecycle hooks, a dashboard tab and an `hermes agora` CLI; installing writes nothing — the three bundled skills are deployed by an explicit `hermes agora setup`.
Good to know before installing
Creates a Hermes profile per worker by asking core to provision it (`hermes profile create --clone`, which copies config.yaml and .env into the new profile as owner-only files, never symlinks to the real credentials); spawns `hermes -p <profile> chat -Q -q` subprocesses to speak in discussions and to run dispatched tasks, which execute as full agents with that profile's toolset, including terminal and file writes inside the project workdir. Those subprocesses receive `--yolo --accept-hooks` ONLY when the project opted in via `agora_start_project(allow_unattended=True)`; the default is off, so a freshly installed team can read, discuss and plan but its flagged writes and shell commands fail closed. Also reads and writes the kanban database (tasks, task_comments, task_events, task_runs, task_links) restricted to its own project boards, including a persistent team-channel task pinned in `scheduled` status, and deletes a project's own tasks when it stops or completes; registers one recurring cron job and writes its runner script to HERMES_HOME/scripts/leader_heartbeat.sh; writes AGENTS.md into the configured project workdir; deploys three bundled skills into HERMES_HOME/skills/collabor
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 agora
Said no? Turn it on later:
hermes plugins enable agora
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).
Guided Desktop workspace in BOTS: tailored questions, reference files, editable instructions and capabilities, version comparisons, model-only trials, and native Bot Chat handoff. Saves specialists as separate Hermes profiles and installs the Builder companion plugin into its own bot profile.
Good to know before installing
"Talk to Builder" auto-creates a hermes-builder profile cloned from the active profile with copied .env/auth.json and copies+enables this plugin there outside the catalog installer (uninstall does not remove that copy); "Save agent" creates new profiles the same way and rewrites their tool/skill selection.
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-agent-builder
Said no? Turn it on later:
hermes plugins enable hermes-agent-builder
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.
Ntfy Approval
Community
Answer Hermes' approval prompts from your phone: once selected with security.approval.transport: ntfy, each dangerous-command prompt arrives as an ntfy push notification with Approve once, Approve for session and Deny…
Answer Hermes' approval prompts from your phone: once selected with security.approval.transport: ntfy, each dangerous-command prompt arrives as an ntfy push notification with Approve once, Approve for session and Deny buttons, and no answer still means deny.
Good to know before installing
Once selected, anyone who can read the ntfy topic can approve dangerous commands (the one-time answer codes are in the notification), so on the public ntfy.sh default the topic name is the only secret and NTFY_APPROVAL_TOKEN is optional; each pending approval publishes Hermes' reason, the redacted command (unless send_command is false), the non-default profile name and one-time answer codes to the configured ntfy server, then reads <topic>-reply and deletes the notification; any failure or timeout is a deny; reads NTFY_APPROVAL_TOPIC/NTFY_APPROVAL_TOKEN from the profile .env, never puts the token in a notification, follows no redirects, writes no files and starts no 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 ntfy-approval
Said no? Turn it on later:
hermes plugins enable ntfy-approval
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).
Jev-style comparative classifier for OrdaPilot. It compares all topic labels and session choices in one batch, including new-topic, ambiguous, and new-session options. It uses calibrated score and margin gates, weighs continuity against context cost and contamination, and abstains when uncertain. OpenRouter is optional for provisional new-label proposals and disabled 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 protean-ordaprompt
Said no? Turn it on later:
hermes plugins enable protean-ordaprompt
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 Routines
Community
A minimal Routines page in Hermes Desktop that turns crontab's five cron.manage actions into a plain-language interface for non-developers - name a routine, pick a schedule, write the prompt, and pause or resume it.
A minimal Routines page in Hermes Desktop that turns crontab's five cron.manage actions into a plain-language interface for non-developers - name a routine, pick a schedule, write the prompt, and pause or resume it. No cron syntax, no service, no database; routine data stays in the host.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-routines
Said no? Turn it on later:
hermes plugins enable hermes-routines
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).
One /crew message becomes verified work on the kanban board. A coordinator owns every card until its proof command exits 0 - one writer per card, an independent verifier, a hard token budget per card, and a live local dashboard of every card, run and tool call.
Good to know before installing
Install.py creates four crew-* profiles cloned from your chat profile (including its .env provider keys and memories), deletes non-crew skills in them, updates crew in other profiles and on Linux starts a loopback dashboard service (127.0.0.1:8799, transcript excerpts; --publish serves it to one tailnet login), restarting it when an upgrade changes the plugin code; it never approves shell hooks itself, but on a terminal offers (y/N) to open each profile's Hermes so Hermes asks for hook consent, first revoking approvals whose hook script changed; on native Windows the service and the optional nightly cron are skipped and the dashboard is started by hand, and proofs run in Git for Windows's bash; a Crew tab in the Hermes dashboard and a native Crew page in Hermes Desktop build that board inside the Hermes backend, including its transcript excerpts, each live card's step count and last tool name, and its acknowledge, Unstuck, Retry, Proof and Stop actions, under /api/plugins/crew/ to anyone with dashboard access; a detached coordinator makes read-only model decisions and runs card proof commands unattended with a scrubbed env, flagged or changed proofs only after the owner answers /cr
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 crew
Said no? Turn it on later:
hermes plugins enable crew
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).
Give every Hermes kanban task a live Discord forum thread with a rewritten status card and append-only event log.
Good to know before installing
Sends task and lifecycle data to the configured Discord webhook (no host allowlist). Cards and event replies use built-in or operator-configured templates and may include identifiers, titles, status, assignment, branch and workspace metadata, relationships and blocking details, comments, event actors, reviewers, reasons, summaries, and configured dashboard links; the comment excerpt length is configurable. Fixed prerequisite announcements additionally send the prerequisite task ID, title, assignee, and up to 140 characters of its body and are not template-configurable. The absolute workspace path is off by default and requires explicit opt-in. Reads the kanban database read-only and stores thread mapping state under <kanban_home>/kanban/plugins/kanban-task-threads/. With an optional existing publisher-profile Discord bot token, reads forum and thread metadata; creates or repairs managed status tags and emojis; replaces applied tags on plugin-managed threads; renames threads; and archives or unarchives them. Discord fetches webhook avatars from the configured HTTPS asset origin. Disclosure — the avatar asset origin defaults to the author-hosted https://diegomarino.github.io/kanban-t
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs KANBAN_TASK_THREADS_WEBHOOK_URL), then asks whether to turn it on.
hermes plugins install kanban-task-threads
Said no? Turn it on later:
hermes plugins enable kanban-task-threads
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 Workflows
Community
Agent-owned workflow graphs for Hermes — a background runner executes a JSON DAG of agent nodes, fan-outs (quorum) and human/machine gates with fingerprint replay-skip resume, cooperative steer, typed failure events…
Agent-owned workflow graphs for Hermes — a background runner executes a JSON DAG of agent nodes, fan-outs (quorum) and human/machine gates with fingerprint replay-skip resume, cooperative steer, typed failure events and compact status payloads; ships a desktop DAG view, an inline transcript card and the authoring skill with measured budget recipes. Stock Hermes; no patched core required.
Good to know before installing
Every workflow run spawns a detached background runner (wf.py run <id>) that survives session end, gateway restart and plugin disable until the graph reaches a boundary or workflow stop; each agent node is a child hermes chat --query-file … --oneshot -Q … inheriting the runner's environment, and a node with profile set runs as that named profile (with its own credentials) only if the target's workflow_team.json lists the launcher; a gate's wait.until_argv runs an agent-authored argv directly from the runner, outside Hermes' tool-approval gate (the engine uses no shell, but the shipped machine-watch and incident-response templates use it to run a shell line read from a fixed-name handoff file under $HERMES_HOME, and release-lifecycle one read from a per-run handoff file in the run dir); the runner makes itself the subreaper of its children and SIGTERM/SIGKILLs any process a node leaves running (its own descendants plus pids registered in the run's .proctree_sidecar.jsonl) when the node finishes, retries or the run stops; run and amend send a one-token ping through Hermes' configured providers to check pinned model routes; at gate.held/run.done/run.failed the runner reads the API ser
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-workflows
Said no? Turn it on later:
hermes plugins enable hermes-workflows
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).
Choose a separate scorer to set the reasoning effort of each Hermes request.
Good to know before installing
Off by default; when a mode is enabled (or on an explicit `/hae probe`), sends the latest user message (or the parent-written subagent goal), truncated to 4000 characters, plus any configured guidance to the scorer you select (TypeSafe Jev at api.typesafe.ai by default, or OpenAI Decisions, OpenRouter, Cloudflare Workers AI, Nace at console.nace.ai, or a custom URL) using that service's key; opt-in settings can also send the target model identity, up to 6 earlier user/assistant text messages (1200 characters each) and a separate continuation question to the same scorer; in Hermes Desktop it also sets the focused chat's session reasoning selector through the gateway `config.set` API after each applied change, and it keeps a prompt-free effort-change history (64 changes × 64 conversations), per-conversation mode overrides (at most 256 conversations) and per-route cache verdicts built from provider token counters (at most 128 routes) in its plugin data directory.
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-adaptive-effort
Said no? Turn it on later:
hermes plugins enable hermes-adaptive-effort
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 Session Lens
Community
Read-only observability for Hermes Desktop: what each session cost and why, its full trace, recurring tool failures, every profile at a glance, provider quotas and service balances, model comparison with cheaper-route…
Read-only observability for Hermes Desktop: what each session cost and why, its full trace, recurring tool failures, every profile at a glance, provider quotas and service balances, model comparison with cheaper-route evidence, and instruction-rule grading.
Good to know before installing
Reads every profile's state.db read-only plus agent logs, cron/gateway state, config.yaml and .env (key names, and the values of keys an adapter uses); with the credentials Hermes' own resolvers return, calls only each configured vendor's usage or balance endpoint (hosts listed in the README), sending Grok CLI client headers to cli-chat-proxy.grok.com and a Claude Code user-agent to api.anthropic.com; Hermes' resolvers may renew Hermes' Codex, Nous and xAI logins and, when Hermes holds no other Anthropic credential, Claude Code's login; runs the local monid CLI when installed; an Anthropic one-token Claude Haiku probe is off by default; writes no Hermes state itself and sends no session content anywhere.
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-lens
Said no? Turn it on later:
hermes plugins enable session-lens
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).
A persistent second model reviews every agent turn. After each turn the plugin hands the transcript to the model you nominate as advisor and delivers its findings as advice in the same session: [NIT], [CONCERN] or [BLOCKER] notes, held back until a later review raises the same point again, so the primary agent is not interrupted by a one-off remark. It reviews, it does not act: the advisor never edits files, calls tools or changes session state, and only reads the turn transcript. This is the backend counterpart of MoA — one extra model, not a committee: the primary agent does the work and the advisor checks it. Port of pi-omplike-advisor (Petr Baudis / pasky), itself rooted in oh-my-pi (Can Boluk). Runs inside the plugin host with no dependencies beyond Hermes itself.
Good to know before installing
Once the plugin is enabled, every completed turn costs one extra completion through Hermes's ctx.llm to the advisor model (the primary agent's provider unless you allow a provider/model override under plugins.entries.advisor.llm), carrying the user message, the final reply, every tool call and tool result in the session so far (each clipped to 500 characters) and the contents of a WATCHDOG.md in Hermes's working directory if one exists; deliverable advice is queued into the CLI session as a user-role message, which starts or interrupts an agent turn; state is kept under $HERMES_HOME/advisor/ and reviews run on one background thread; no other network, files or 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 advisor
Said no? Turn it on later:
hermes plugins enable advisor
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).
Signed messaging with paired Hermes and OpenClaw agents, with receiver-controlled live and opt-in non-YOLO headless delivery.
Good to know before installing
Runs a loopback-only Node receiver when listen_port is set (you expose only its HTTPS receive route); messages from paired peers become agent turns in the sessions you approve and may cause tool use, and opt-in background delivery runs them in non-YOLO sessions only; smart scanning sends message text through your configured provider; ClawReef Public Groups use a plaintext relay that ClawReef can read; identity keys, peer credentials, holds and receipts live in the profile's plugin-data/antenna (0700/0600) and backups contain credentials; policy and storage commands rewrite config.yaml (comments and formatting are lost).
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 antenna
Said no? Turn it on later:
hermes plugins enable antenna
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).
Pushover as an outbound-only gateway platform, plus opt-in agent lifecycle notifications (finished, questions, errors, approvals, kanban blockers, Hermes's sudo password prompt) via Pushover and/or native notify-send, managed with /notifications.
Good to know before installing
Sends HTTPS requests to api.pushover.net only, carrying your Pushover app token, user key and notification text (when lifecycle notifications are enabled, excerpts of agent replies, clarify questions, approval commands, the command waiting on the sudo password prompt (redacted by Hermes; never the password) and kanban block reasons; PUSHOVER_NOTIFY_QUESTION=minimal suppresses all but kanban reasons); send_message can address any Pushover user or group key; runs notify-send (argv, no shell) when native notifications are enabled; writes an unrotated log under $HERMES_HOME/logs and settings.json under $HERMES_HOME/plugin-data, and $HERMES_HOME/.env only from the interactive setup wizard. Outbound-only, no inbound or approval path, no telemetry, no background processes.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs PUSHOVER_APP_TOKEN, PUSHOVER_USER_KEY), then asks whether to turn it on.
hermes plugins install pushover-hermes-plugin
Said no? Turn it on later:
hermes plugins enable pushover-hermes-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.
Model Drift Watch
Community
Scheduled check that the model you use in Hermes has not quietly got worse: 34 fixed, exactly graded questions (reasoning, instruction following, Japanese, plus your own) run through Hermes cron, each run tested…
Scheduled check that the model you use in Hermes has not quietly got worse: 34 fixed, exactly graded questions (reasoning, instruction following, Japanese, plus your own) run through Hermes cron, each run tested against the same model's own baseline with an exact per-question test and a same-day confirmation run, and a message only for a confirmed drop, a changed served model or a failed measurement. Not yet tried against a real LLM API (checked with a local mock model and real Hermes cron).
Good to know before installing
Each check calls your own model through ctx.llm on your bill, capped per check by the plugin (default 120,000 tokens / $0.50, no daily cap; the agent can start checks itself via the model_drift tool, and the scheduled agent turn is extra); price lookup goes through Hermes's pricing code (may fetch OpenRouter/models.dev prices); 10 optional code questions, off by default, run model-written Python in a limited child process (not a hostile-code sandbox) including in unattended cron runs when enabled; `schedule` creates one Hermes cron job that survives plugin removal (run `unschedule` first); writes run history to plugin-data/model-drift-watch; 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 model-drift-watch
Said no? Turn it on later:
hermes plugins enable model-drift-watch
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.
Cabinet
Community
Tell Cabinet the job you need done and it answers with the smallest setup that does it (one chat, a skill, a routine, a Bot or a crew), shows which answers led there, then helps you act: add one of botcabinet.com's 20…
Tell Cabinet the job you need done and it answers with the smallest setup that does it (one chat, a skill, a routine, a Bot or a crew), shows which answers led there, then helps you act: add one of botcabinet.com's 20 Bots (each with its test record shown) as a Hermes profile, plan a new Bot line by line, or set up a crew of Bots in a handoff order with blocked Kanban cards. Everything Cabinet makes can be removed again from My Bots, and a Bot that Hermes's own Bots catalog carries is handed over to it, never duplicated.
Good to know before installing
Fetches its Bot catalog from https://botcabinet.com/catalog.json on open and Refresh (data only, 2 MB cap) and, after you confirm, creates Hermes profiles whose instructions (SOUL.md) come from that catalog; can create and archive Kanban cards for a crew; deletes only profiles it created that you have not changed; reads ~/.hermes/profiles and hashes profile files to track what it made; calls private Hermes modules (hermes_cli.profiles, kanban_db), so a Hermes update can break it; no shell, credentials, telemetry or self-updates.
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 bot-cabinet-v2
Said no? Turn it on later:
hermes plugins enable bot-cabinet-v2
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.
Custodian
Community
Autonomous operations monitor for a Hermes install: scans gateway logs, cron jobs, skill journals and agent data directories, classifies findings against a 27-fingerprint registry, auto-repairs Tier 1 problems…
Autonomous operations monitor for a Hermes install: scans gateway logs, cron jobs, skill journals and agent data directories, classifies findings against a 27-fingerprint registry, auto-repairs Tier 1 problems, escalates the rest, and keeps an append-only issue ledger. Ships /custodian (status, scan, issues, repair, verify, schedule, confidence, init, escalation-runner), four scan/health tools and a grid dashboard.
Good to know before installing
Reads gateway logs, cron job state and per-skill journal files under HERMES_HOME to build its findings, and writes repair actions and an issues ledger back there; it performs no network I/O and holds no credentials. Disclosure — /custodian init registers 3 recurring agent cron jobs (deep scan 4×/day, cron-health 4×/day, escalation runner every 30 min on weekdays).
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 custodian
Said no? Turn it on later:
hermes plugins enable custodian
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.
Alan's Way Plugin
Community
Idle check-ins from the primary bot of a Hermes gateway on a Linux machine or a macOS guest VM: when the bound Telegram chat has been quiet for two hours, during 08:00-22:00 in the user's timezone, the bot checks in…
Idle check-ins from the primary bot of a Hermes gateway on a Linux machine or a macOS guest VM: when the bound Telegram chat has been quiet for two hours, during 08:00-22:00 in the user's timezone, the bot checks in once (does one safe step and reports it, suggests one, or asks one question), backing off when unanswered. The model tool can only make check-ins quieter; more often, resume and wider hours are operator-only via /proactivity or the CLI. After install, the workspace-setup skill walks the agent through setting up Alan's Workspace (a separate desktop app for the user's computer: macOS or Windows) and Tailscale; desktop input goes only through Hermes's approval-gated computer_use tool.
Good to know before installing
Once the gateway connects Telegram, a background thread checks every 60 seconds. When the bound Telegram DM has been quiet (2 h by default, doubling per unanswered check-in, 08:00-22:00 user time), it injects an internal user-role prompt into that chat (needs plugins.entries.alans-way.allow_gateway_injection, which setup sets), so the bot runs a turn on its own and may take one "safe, reversible" step; the user still approves tool calls in Telegram. Its pre_llm_call/post_llm_call hooks see every session's turns and store the bound chat's activity timestamps in plugin state; optional cross-bot export adds the separate storage disclosed below. On first load it reads $HERMES_HOME/companion/proactivity/proactivity.sqlite3 once, read-only. The plugin itself makes no network calls. The workspace-setup skill has the agent fetch this repo at the catalog pin into ~/alans-way-agents (or reuse a clean clone there) and hand a JSON setup plan to the human in Alan's Workspace. The app runs setup.sh through an external SSH process outside the gateway, checks the exact repoRef and desktopRef and rejects tracked checkout changes; the agent must never run setup or even --verify in its gateway termin
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 alans-way
Said no? Turn it on later:
hermes plugins enable alans-way
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 Desktop page for the focused chat: the main agent and its subagents, background commands and a Replay of file edits.
Good to know before installing
Its local dashboard routes serve the file-edit contents (Replay) and background-command output tails of the chat you view to the Desktop page; reads state.db read-only.
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 agent-station
Said no? Turn it on later:
hermes plugins enable agent-station
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).
Hermes gateway integration for DeskRPG virtual offices, with profiles, kanban, cron, artifacts and NPC skill management. Install it through the DeskRPG setup wizard. Optional (off by default): when enabled by the operator, links the plugin into every profile so kanban workers and cron runs can save artifacts.
Good to know before installing
NPC skill management runs hermes skills/curator commands as background subprocesses per profile and edits that profile's skills, config.yaml and memory files; creating new review-policy kanban cards needs a review-policy API that upstream Hermes does not ship (the README points at the author's hermes-agent fork for it), and that feature stays inert on upstream.
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 deskrpg
Said no? Turn it on later:
hermes plugins enable deskrpg
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.
Nerve
Community
Nerve is a supervisory nervous system for Hermes Agent with provider-neutral Jev, Laya, and OpenJev Reflex backends, evidence-backed Kanban supervision, context governance, token-budget trajectory control, and durable…
Nerve is a supervisory nervous system for Hermes Agent with provider-neutral Jev, Laya, and OpenJev Reflex backends, evidence-backed Kanban supervision, context governance, token-budget trajectory control, and durable SSH workers.
Good to know before installing
The default Reflex backend is hosted Jev; with the default settings (enabled / admission_enabled on) each turn's user prompt (up to 12k characters) and redacted tool/result previews are sent to the configured Jev provider (OpenRouter Decisions / TypeSafe Jev) using your OPENROUTER_API_KEY or TYPESAFE_API_KEY, spending your credits on every turn. Laya and OpenJev can be configured as local/self-hosted backends. The operator-only nerve setup CLI can copy a local HermesContextBus checkout into HERMES_HOME/plugins/hermes-context-bus and runs hermes plugins enable/disable for that plugin when a profile is saved; the model cannot trigger this.
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 nerve
Said no? Turn it on later:
hermes plugins enable nerve
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.
Crontab Ref
Community
@crontab: context references that explain a cron expression for the model: @crontab:"0 9 * * 1-5" (or a shortcut such as @crontab:@daily) attaches a plain-words reading ("At 09:00 on Monday through Friday."), each…
@crontab: context references that explain a cron expression for the model: @crontab:"0 9 * * 1-5" (or a shortcut such as @crontab:@daily) attaches a plain-words reading ("At 09:00 on Monday through Friday."), each field on its own row, whether Hermes's /cron takes it as a cron expression (shortcuts, ? and 5#3 are not), its next five runs in Hermes's timezone setting worked out the way cron/jobs.py computes next runs, and notes on day of month OR day of week, * in the minute field, steps that do not divide the hour or day, days 29-31 and 7 as Sunday; the TUI and Desktop composer suggest examples and preview an expression as you type it. The reading comes from croniter, the library Hermes's scheduler uses.
Good to know before installing
Reads only the text of the reference itself, the system clock and Hermes's timezone setting (HERMES_TIMEZONE, else timezone from the loaded config through hermes_cli.config), using croniter (already installed with Hermes) and Python's standard library; no network, no files read or written, no subprocess, no credentials read, no cron job created, changed or run; the @crontab: reference and its explanation become part of the message sent to your model provider and saved in the session history; register() only adds the @crontab: reference provider.
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 crontab-ref
Said no? Turn it on later:
hermes plugins enable crontab-ref
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).
Cross-profile agent dispatch for Hermes Agent — 12 tools for agents talking to agents: async dispatch with SSE completion, synchronous multi-turn chat, model-selectable in-process subagents, a durable SQLite run ledger, fail-closed per-target model-route discovery, and host-owned bare LLM inference.
Good to know before installing
Sends task text and bearer tokens to the Hermes API servers you configure (plaintext HTTP permitted, warn-only); stores full dispatch text in a local SQLite ledger; delegate_subagent may use any provider credential you have configured.
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-herald
Said no? Turn it on later:
hermes plugins enable hermes-herald
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).
TypeSafe Jev semantic governance for Hermes' native Curator: classifies relationships between complete skill packages, produces content-hash-bound, fail-closed consolidation plans, and locally guards background destructive skill_manage calls while Hermes retains control of backups and mutations. A profile-scoped 60-second lifecycle debounce coalesces skill changes into dry refreshes.
Good to know before installing
No egress occurs by default; after allow_content_egress is explicitly enabled, redacted bounded skill content is sent to the configured TypeSafe, OpenRouter, or custom Jev endpoint and may spend provider credits. Automatic refreshes never apply mutations, and missing, stale, or incomplete evidence fails closed.
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 jev-curator
Said no? Turn it on later:
hermes plugins enable jev-curator
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 Model Switcher
Community
Choose models across Hermes profiles from a Dashboard tab: a per-profile picker built on host-supplied model data (SDK-authenticated GET /api/model/options), a preview of provider/model intent across every supported…
Choose models across Hermes profiles from a Dashboard tab: a per-profile picker built on host-supplied model data (SDK-authenticated GET /api/model/options), a preview of provider/model intent across every supported model-selection slot (main, delegation, auxiliary, judge, fallback, MoA, cron, plugin and specialist), and one-click apply or revert with presets. Main-slot preview shows intended provider/model, not the exact persisted diff; the exact diff is shown only after host readback.
Good to know before installing
Its apply route reads and edits the profiles' config.yaml (that is the plugin's function) through public seams only: POST /api/model/set for main and compatible auxiliary slots, and public hermes_cli.config load/save under the target home for other slots; credential presence checks use public profile-scoped secret helpers (agent.secret_scope), and profile discovery uses public hermes_constants. The plugin makes no direct third-party requests and opens no provider caches or pricing registries directly, but its browser tab does call the host's /api/model/* routes through the Dashboard SDK, and the host options route may itself initiate provider or pricing I/O even without an explicit refresh request, so reads are not guaranteed cache-only. It runs no shell commands or background processes and reports nothing. The private undo journal stores a full pre-change snapshot of each config it edits, which can contain sensitive fields including embedded credentials. Saved presets also persist reviewed change values, potentially including inline credentials or credential-bearing base URLs, in presets.json (0600) under get_hermes_home()/state/hermes-model-switcher/ (0700). The host write route
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-model-switcher
Said no? Turn it on later:
hermes plugins enable hermes-model-switcher
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).
A Hermes Desktop page for running a fleet - topology, model traffic, handoffs, traces, merge requests and conformance checks in one place.
Good to know before installing
Reads hermes-metrics-dash's <hermes root>/metrics/metrics.db, the kanban board, every profile's config.yaml (plugin enable state, rolectl-mcp entries, default model) and plugin-data/gitlab-mr/device-aliases.json, all read-only; calls your GitLab (host and token from the plugin settings or GITLAB_HOST/GITLAB_TOKEN), the local model router (MODEL_ROUTER_URL, default 127.0.0.1:8867) and LM Studio (LMSTUDIO_URL, default 127.0.0.1:1234); runs git status/rev-parse/ls-files in the project folders it checks and shows matching lines (including any keys found) on the page. Page buttons create, assign, schedule, unblock and close kanban cards and start their workers at once, write <hermes root>/conformance/conformance.yaml, and "Propose a rule" pushes a branch and opens a merge request on the standard's GitLab project. A hook on every kanban dispatcher tick starts cards scheduled from the page; with alert_target set it posts new attention items through hermes send; with drift_action: automatic it files and starts a fix card for drift_profile for each drifting host with a verified report (at most daily) carrying the standard's remediate commands. With Activity summaries on (off by default), Ac
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 operations
Said no? Turn it on later:
hermes plugins enable operations
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).
Fleet-wide provider and model presets with CLI and Hermes Desktop support.
Good to know before installing
Writes model/provider keys into the config.yaml of the profiles you select (backup taken first).
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 protean-model-sync
Said no? Turn it on later:
hermes plugins enable protean-model-sync
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 System One / Laya Typed Decisions control plane for Hermes Agent. Sends bounded turn data to a configurable sidecar for reversible OFF/Shadow/Canary routing decisions, with explicit Canary acknowledgement and fail-open behavior.
Good to know before installing
Executes nothing and does not start the sidecar. In Shadow/Canary mode, Search and Model Tier may POST the current task plus bounded recent conversation context; Notification Shadow may POST the completed turn's final assistant response (up to 6000 chars) plus lifecycle metadata. The default sidecar URL is loopback 127.0.0.1:8787 but is user-configurable to any host and no auth header is added. Notification is observation-only: the plugin never sends a push/message/webhook and persists decision metadata, not raw response text. Its only request mutations, in acknowledged Canary mode on the first provider call of a turn, are removing web_search/web_extract tools for audited deterministic no-Web rules and (off by default) lowering reasoning_effort for gemini-3.8-flash-tiered on audited hard-fast rules. The sidecar (same repo, separate pip install, Apple-Silicon MLX/CoreML) is a text classifier that downloads a pinned Hugging Face model.
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 local-system-one-hermes
Said no? Turn it on later:
hermes plugins enable local-system-one-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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Kanban Graph
Community
Live, read-only dependency graph of the Hermes kanban boards in Hermes Desktop: every board as a band, tasks as cards, dependencies as arrows with implied ones folded away.
Live, read-only dependency graph of the Hermes kanban boards in Hermes Desktop: every board as a band, tasks as cards, dependencies as arrows with implied ones folded away. Click a task to light up its whole lineage with runs, last failure and the running worker's latest tool calls; deep links open a task directly, and a stdlib CLI renders the same graph as a standalone HTML file. Zero API keys, zero model tokens.
Good to know before installing
Reads every kanban board database and, for running tasks, the assignee profile's state.db (the kanban worker session's latest assistant messages and tool-call arguments), read-only, and shows them in Desktop through its own local dashboard routes.
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 kanban-graph
Said no? Turn it on later:
hermes plugins enable kanban-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).
Manus-style planning flow — the agent plans in steps and marks them as it works, with a live desktop pane.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install handflow
Said no? Turn it on later:
hermes plugins enable handflow
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.
Pstack
Community
Engineering rigor stack: poteto-mode orchestrator with 17 playbooks, plus how, architect, interrogate, swarm, unslop, and 46 other skills and principles.
Engineering rigor stack: poteto-mode orchestrator with 17 playbooks, plus how, architect, interrogate, swarm, unslop, and 46 other skills and principles.
Good to know before installing
Skills only, no tools or network calls of their own; when the user asks, the setup-pstack skill changes Hermes `delegation` model/provider/reasoning settings via `hermes config set`, the autopilot, shipping and babysit playbooks push and force-push the agent's own branches, squash-merge pull requests and arm hourly Hermes cron jobs to watch them, and the reflect skill files backlog issues in your team's tracker without asking per item.
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 pstack
Said no? Turn it on later:
hermes plugins enable pstack
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 project ownership and bounded initiative management for Hermes fleets.
Good to know before installing
A `pre_llm_call` hook adds a project's saved rules, decisions and facts to turns of bots assigned to that project; objective checks run allowlisted local programs only at autonomy level 3+ and GitHub objectives shell out to your own `gh api`; it creates and edits Hermes Kanban tasks through Hermes' internal kanban modules (title/body/tenant written directly to kanban.db), keeps its own SQLite DB under `<Hermes home>/plugin-data/hermes-dockyard/`, and its optional HTTP API (`/stewardship/v1`, 127.0.0.1) stays closed until you set a bearer token.
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-project-stewardship
Said no? Turn it on later:
hermes plugins enable hermes-project-stewardship
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).
Dataset import, adaptation, augmentation, translation, synthetic generation, and AutoScientist fine-tuning through the hosted Adaption MCP. Portable Agent Plugins v1 package with three workflow skills; the MCP server is added separately with OAuth (or an API key for headless use).
Good to know before installing
Skill-only, no code; the MCP tools call api.prod.adaptionlabs.ai, and launches spend Adaption credits (the skills request a cost estimate first, Hermes does not enforce it). Hermes does not prompt before those tools unless the server is configured with trust: untrusted.
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 adaption
Said no? Turn it on later:
hermes plugins enable adaption
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.
Chat Length
Community
Tells the user when a chat is getting too long and hands them a short opener for a fresh chat; the new chat pulls the earlier context itself via session_search, no handover document.
Tells the user when a chat is getting too long and hands them a short opener for a fresh chat; the new chat pulls the earlier context itself via session_search, no handover document. Fill level from real provider token counts, measured against Hermes' compaction point by default; notices at 70 % and 90 % (configurable), once each per chat, re-armed after compaction, never in cron, subagent, kanban, batch or webhook runs. Notice in the conversation language, English or German.
Good to know before installing
On the turn that crosses a threshold, pre_llm_call adds a one-turn instruction to that turn's user message (never the system prompt; replayed byte-identical, so prompt caching stays intact); post_api_request stores per-session token counts, model and provider name and which notice fired (no message content) under HERMES_HOME/plugin-data/chat-length/, pruned after 30 days; reads the session title read-only from state.db and the compression settings read-only from config.yaml; no network calls, no tools, no dependencies.
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 chat-length
Said no? Turn it on later:
hermes plugins enable chat-length
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).
Parallel AI task orchestrator. Paste a task list into the desktop panel; Hermes phases it into dependency-ordered groups through the agent_batch_plan / agent_batch_phase tools (or you group it yourself in one click), then each phase dispatches one independent coding agent per task to a GitHub Actions workflow in a repo you name — own branch, own PR — and the panel tracks the runs and the PRs. GITHUB_TOKEN is the only required credential; AGENT_BATCH_REPO, AGENT_BATCH_WORKFLOW, AGENT_BATCH_MODEL and AGENT_BATCH_STATE are optional (the last is a directory override for the plan file, not a secret) and each can be set per plan in the panel instead.
Good to know before installing
Hermes can read and rewrite the stored phase plan through the agent_batch_plan / agent_batch_phase tools, but dispatch is always a confirmed click in the panel. Each dispatch fires a GitHub workflow_dispatch with your GITHUB_TOKEN (Actions + pull-requests write) on the repo you name. The workflow you copy into that repo installs third-party coding-agent CLIs (cline by default; the others are unpinned npm packages) and runs them unattended, with auto-approve / skip-permissions, repo write access and your provider secrets. They push real branches and open real PRs, and your task text and repository code go to that runner's model vendor. LLM cost belongs to the runner: cline spends Cline Credits or a BYOK key, opencode free models need its zen relay, kilo needs an active Kilo Go subscription (keyless CI runs fail), and claude-code / codex / dsh need their own keys.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs GITHUB_TOKEN), then asks whether to turn it on.
hermes plugins install agent-batch
Said no? Turn it on later:
hermes plugins enable agent-batch
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 non-blocking questions with exact answer binding and gateway continuation.
Good to know before installing
Its pre_gateway_dispatch hook sees every gateway message and consumes only `dq <id> …` answers from the stored recipient; with `enable_tool` on, the model can send questions to any chat the gateway already authorizes, and a question marked continue_agent resumes that chat's agent with the user's answer; questions and answers are stored unencrypted in $HERMES_HOME/deferred-questions/questions.sqlite3; it calls private gateway and adapter methods, so a Hermes update can break delivery until it is re-pinned.
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 deferred-questions
Said no? Turn it on later:
hermes plugins enable deferred-questions
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).
LLM Council (karpathy/llm-council) as a Hermes plugin. Four fixed advisor seats (First-Principles Analyst, Skeptic, Pragmatist, Researcher) answer in parallel, anonymously review and rank each other, and a Chairman model synthesizes the final answer. Members borrow your existing provider credentials - no API keys. Registers a Council group in every model menu, a council_deliberate tool, /council, hermes council CLI, and a desktop panel.
Good to know before installing
Council_deliberate and the Council model fan each prompt (as a session model, the whole conversation) out to every seat, judge and chairman model you assign, up to 2N+1 billed calls per turn on your existing provider credentials; it also adds a non-secret "council" marker row to auth.json and keeps run history in $HERMES_HOME/council/runs/.
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-council
Said no? Turn it on later:
hermes plugins enable hermes-council
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.
