NousResearch/hermes-official-plugins

The official plugins for Hermes Agent, built and maintained by Nous Research.
One repo, every first-party plugin, installed in one line from the Hermes plugin catalog.

Hermes Agent is the self-improving AI agent from Nous Research. It writes skills from experience and keeps improving them as it works, remembers what matters across sessions, and runs where you are: the terminal, the Hermes Desktop app, Telegram, Discord, Slack, WhatsApp, Signal and more, all through one gateway. You can bring any model (Nous Portal, OpenRouter, Anthropic, OpenAI, your own endpoint) and run it on a laptop, a $5 VPS or serverless infrastructure.

curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash

The Hermes core keeps the parts every user needs: the agent loop, memory, skills, the gateway, model routing and the tool runtime. Everything specific to one product, one vendor or one hobby belongs in a plugin, which you install when you want it and which ships on its own schedule.

That gives you:

• Smaller, faster installs. You don't download a Spotify client to run a coding agent.
• Fixes without waiting for a release. A plugin ships a fix as soon as it's reviewed. It doesn't wait for the next Hermes version.
• A clear owner for each integration. Vendor plugins live with the vendors who build them, community plugins with their authors, and Nous's own plugins live here.

The Hermes plugin catalog is the reviewed index of everything you can install: model providers, memory providers, messaging platforms, Desktop extensions, voice, web and automation tools. It has hundreds of entries from Nous, vendors and the community. Each entry is pinned to a reviewed commit, so what you install is exactly what was reviewed, and an update moves you only when a new pin passes review.

hermes plugins search            # browse the catalog
hermes plugins info spotify      # what it does, what it needs, which commit
hermes plugins install spotify   # install at the reviewed pin
hermes plugins update spotify    # follow the catalog to the next reviewed pin

Hermes Desktop has the same catalog under Capabilities → Plugins.

Catalog entries come in two tiers:

Home Assistant hermes plugins install homeassistant A gateway platform plus four tools. Hermes watches your Home Assistant event bus, reacts to the state changes you care about, controls devices over the REST API, and replies as Home Assistant notifications. Cron jobs can deliver straight to your phone with deliver=homeassistant. ha_list_entities · ha_get_state · ha_list_services · ha_call_service	Spotify hermes plugins install spotify Seven tools over the Spotify Web API: playback, Spotify Connect devices, the queue, search, playlists, albums and your library, plus hermes spotify login for a loopback PKCE login with your own Spotify developer app. Playback control needs Premium. spotify_playback · spotify_devices · spotify_queue · spotify_search · spotify_playlists · spotify_albums · spotify_library
Claude Subscription DirectSDK experimental hermes plugins install claude-subscription-directsdk A model provider that runs Hermes turns on your Claude Pro or Max subscription through the official Claude Code CLI, with no separate API key or per-token bill. Hermes keeps its own agent loop, tools, approvals and compaction; the plugin drives the logged-in claude binary as a request-scoped model client, and refuses cleanly with an install hint when Claude Code is missing. Pick it in hermes model → Claude Subscription DirectSDK (Experimental)	Telegram Business Mode hermes plugins install hermes-telegram-business Turns Hermes into an observe-with-approval secretary for your Telegram Business account. It drafts replies to your customers, and nothing is sent until you approve it. Gateway platform add-on · owner approval on every reply
Memory Wiki hermes plugins install hermes-memory-wiki A dashboard and Desktop tab that turns your local session history into browsable subject pages and daily logs, plus a read-only audit panel for MEMORY.md and USER.md. Dashboard tab · reads local history, writes nothing	Blender hermes plugins install blender The official Blender Lab MCP server over stdio, pinned to upstream, with a Blender workflow skill, so Hermes can read and change your Blender scene. Needs Blender 5.1+ with its MCP add-on, Git and uv. Its tools run Python inside Blender, so use trusted workflows. MCP server + skill · Windows, macOS, Linux
Snyk hermes plugins install snyk Scan code (SAST), dependencies, container images, IaC and SBOMs through Snyk's first-party MCP server, with the snyk-security-scan workflow skill. Needs Node.js/npm and a free Snyk account. MCP server + skill · browser login via snyk_auth	TouchDesigner hermes plugins install touchdesigner Drive a live TouchDesigner session through 404.zero's free twozero MCP server, which runs inside TouchDesigner itself, with the touchdesigner-mcp workflow skill and 20+ reference files (operators, GLSL, audio-reactive, instancing) bundled. MCP server + skill · TouchDesigner on macOS or Windows
Accent Picker desktop hermes plugins install accent-picker An OKLCH colour wheel in the Hermes Desktop status bar. Drag it and the whole theme retints live, so theme authors can try accents in place. The colour is scratch state and never persisted. Desktop plugin · status bar + palette commands	Langfuse hermes plugins install langfuse Traces every Hermes turn to Langfuse: one span per turn, one generation per LLM call with usage and cost from Hermes' own pricing (cache and reasoning tokens included), one observation per tool call and subagent. Content capture is sanitized by default, with metadata-only and full modes. Observability hooks · Langfuse Cloud or self-hosted
More on the way Official plugins move in here as they leave Hermes core or join from their own repos. Browse everything else, from Nous, vendors and the community, in the plugin catalog.

Every plugin here used to live somewhere else: Home Assistant and Spotify were built into Hermes core and then briefly had their own repos, Langfuse shipped bundled with core as observability/langfuse, and the rest each had a standalone NousResearch/hermes-* repo. You don't need to do anything.

• You used the built-in Home Assistant, Spotify or Langfuse: hermes update, or the first start after updating, installs the plugin from the catalog with your existing config, env vars and login.
• You installed it from the catalog: the catalog now points here, so hermes plugins update <name> moves your install to this repo and keeps your files.
• You installed it by URL (for example hermes plugins install NousResearch/hermes-homeassistant): reinstall once from the catalog with hermes plugins install <name> --force to follow future updates. The old repos are archived and get no new fixes.

hermes-official-plugins/
├── assets/                         # README and catalog art
├── homeassistant/                  # one self-contained plugin per directory
│   ├── plugin.yaml                 #   manifest: name, tools, env vars, Hermes version
│   ├── __init__.py                 #   register(ctx)
│   ├── pyproject.toml              #   plugin dependencies
│   └── tests/                      #   the plugin's own suite
├── blender/                        # portable plugins: plugin.json + mcp.json + skills/
├── accent-picker/                  # Desktop plugins: plugin.yaml + desktop/plugin.js
└── ...

Each directory is a complete Hermes plugin. The catalog installs one by repo + subdir at a pinned commit, and Hermes fetches only that directory (a blobless sparse clone), so installing Spotify never downloads Home Assistant.

Every plugin is tested against current Hermes core on Linux, macOS and Windows, on every push and pull request. A nightly run catches core changes that break a plugin before users see them.

git clone https://github.com/NousResearch/hermes-agent
git clone https://github.com/NousResearch/hermes-official-plugins
cd hermes-official-plugins/spotify
HERMES_AGENT_REPO=../../hermes-agent PYTHONPATH=../../hermes-agent python -m pytest -q

To try your local checkout in a real Hermes, install the directory: hermes plugins install ./spotify --force.

Releasing: merge to main, then open a PR on hermes-agent that bumps the plugin's sha: in plugin-catalog/<name>.yaml. The catalog pin is the release; every installed copy moves on its next hermes plugins update.

Issues: open them here and name the plugin in the title ([spotify] ...). Bugs in Hermes core belong on hermes-agent.

Plugins are plain Python with a plugin.yaml. Start with the plugin guide and the example plugins, then submit yours to the catalog.

_{MIT licensed · Built by Nous Research · ☤}