From bare terminal to agentic workstation: a hands-on guide to Hermes Agent's official plugins

Nous Research's Hermes Agent is a self-improving AI agent that lives in your terminal, your desktop and your chat apps — and its new official plugin repo turns it from a clever chatbot into a workstation. This tutorial installs the agent and wires up four first-party plugins: Spotify, Home Assistant, a Claude-subscription model provider and Langfuse tracing.

• Who: Nous Research — repo NousResearch/hermes-official-plugins, MIT license.
• What: first-party plugins for the Hermes Agent, a self-improving agent that runs in the terminal, the Hermes Desktop app and Telegram/Discord/Slack/WhatsApp/Signal through one gateway.
• When: repo created 2026-10-10; 378 stars as of 2026-10-22.
• Core commands: hermes plugins search, hermes plugins info <name>, hermes plugins install <name>, hermes plugins update <name>.
• This tutorial installs 4 plugins: Spotify (7 tools, Premium for playback), Claude Subscription DirectSDK (experimental, runs on a Claude Pro/Max subscription), Home Assistant (4 tools), Langfuse (per-turn spans with usage and cost).
• Security model: every catalog entry is pinned to a reviewed commit; updates move you only when a new pin passes review.

AI agents spent a year getting big. Now they're getting modular. Nous Research — the team behind the Hermes model family — just pulled every first-party integration for its Hermes Agent out of the core and into one repository: hermes-official-plugins, MIT-licensed, 378 GitHub stars twelve days after creation.

The reasoning is sound: the agent keeps only what everyone needs (the agent loop, memory, skills, the gateway, model routing, the tool runtime), and everything tied to one vendor, product or hobby becomes a plugin that ships on its own schedule. A Spotify fix doesn't wait for the next Hermes release, and you don't download a Spotify client to run a coding agent. In this tutorial you'll install the agent and wire up four official plugins — music, models, home control and observability — in about half an hour.

What you'll need

• macOS, Linux or Windows with a terminal.
• curl for the installer.
• A model backend: an API key for Nous Portal, OpenRouter, Anthropic or OpenAI — or a Claude Pro/Max subscription (step 4 turns that into your model provider, no API key).
• Optional, per plugin: a Spotify account (Premium if you want playback control), a reachable Home Assistant instance, a free Langfuse account.

Step 1 — Install Hermes Agent

Hermes Agent is Nous Research's self-improving agent: it writes skills from experience, remembers what matters across sessions, and runs anywhere — laptop, a $5 VPS or serverless. Install it:

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

Run hermes model to pick your model backend (or point it at your own endpoint). If you have a Claude Pro or Max subscription, skip the API key entirely — step 4 covers that.

Step 2 — Browse the plugin catalog

The Hermes plugin catalog is the reviewed index of everything installable: model providers, memory providers, messaging platforms, desktop extensions, voice, web and automation tools, from Nous, vendors and the community. Three commands run it:

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 exposes the same catalog under Capabilities → Plugins. Entries come in two tiers: official (this repo, one directory per plugin) and community (the author's own repo, reviewed on entry). Every entry is pinned to a reviewed commit — what you install is exactly what was reviewed.

Step 3 — Give it music: the Spotify plugin

hermes plugins install spotify
hermes spotify login

The login uses a loopback PKCE flow against your own Spotify developer app. The plugin adds seven tools over the Spotify Web API: spotify_playback, spotify_devices, spotify_queue, spotify_search, spotify_playlists, spotify_albums and spotify_library. Ask Hermes to find a playlist and start it on a named Spotify Connect device — playback control needs Spotify Premium, which the README states plainly.

Step 4 — Spend nothing on tokens: the Claude Subscription DirectSDK plugin

This one is marked experimental, and it's the most interesting in the catalog for cost reasons:

hermes plugins install claude-subscription-directsdk

Then open hermes model and pick Claude Subscription DirectSDK (Experimental). Hermes keeps its own agent loop, tools, approvals and compaction; the plugin drives your logged-in claude binary as a request-scoped model client. No separate API key, no per-token bill — it runs Hermes turns on your Claude Pro or Max subscription. If Claude Code isn't installed, it refuses cleanly and prints an install hint instead of failing mid-turn.

Step 5 — Connect your house: the Home Assistant plugin

hermes plugins install homeassistant

This is a gateway platform plus four tools: ha_list_entities, ha_get_state, ha_list_services, ha_call_service. 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.

Step 6 — Watch it think: the Langfuse plugin

hermes plugins install langfuse

One install, and every Hermes turn is traced: 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. Works with Langfuse Cloud or a self-hosted instance — useful the moment you start wondering what an agent actually cost you.

What you built

A modular agentic workstation: one lean agent core, four capabilities you chose, each installed in one line and each updatable independently of the core. Browse the other 13 official plugins the same way — Blender and TouchDesigner drive creative tools over MCP, Snyk scans your code, agent-importers absorbs your OpenClaw/Claude Code/Codex/Cursor setup, and bubblewrap sandboxes the terminal backend on Linux.

Honest limitations

• Spotify playback control needs Premium and your own Spotify developer app — the plugin won't fix licensing.
• The Claude Subscription DirectSDK plugin is experimental and needs the logged-in Claude Code CLI; it is not a general replacement for an Anthropic API key.
• Home Assistant integration needs a reachable instance; Hermes can only see what your network lets it see.
• You still need a model backend — plugins add capabilities, not intelligence. Catalog pins are a security feature, but they also mean a fix waits for review before it reaches you.
• Migrating? If you used the old built-ins, hermes update moves you automatically — except hermes mcp serve, which becomes hermes plugins install mcp-serve plus an args change from ["mcp", "serve"] to ["mcp-serve"] in your MCP client config.