--- sidebar_position: 12 sidebar_label: "Built-in Plugins" title: "Built-in Plugins" description: "Plugins shipped with Hermes Agent that run automatically via lifecycle hooks — disk-cleanup and friends" --- # Built-in Plugins Hermes ships a small set of plugins bundled with the repository. They live under `/plugins//` and load automatically alongside user-installed plugins in `~/.hermes/plugins/`. They use the same plugin surface as third-party plugins — hooks, tools, slash commands — just maintained in-tree. See the [Plugins](/user-guide/features/plugins) page for the general plugin system, and [Build a Hermes Plugin](/guides/build-a-hermes-plugin) to write your own. ## How discovery works The `PluginManager` scans four sources, in order: 1. **Bundled** — `/plugins//` (what this page documents) 2. **User** — `~/.hermes/plugins//` 3. **Project** — `./.hermes/plugins//` (requires `HERMES_ENABLE_PROJECT_PLUGINS=1`) 4. **Pip entry points** — `hermes_agent.plugins` On name collision, later sources win — a user plugin named `disk-cleanup` would replace the bundled one. `plugins/memory/` and `plugins/context_engine/` are deliberately excluded from bundled scanning. Those directories use their own discovery paths because memory providers and context engines are single-select providers configured through `hermes memory setup` / `context.engine` in config. ## Bundled plugins are opt-in Bundled plugins ship disabled. Discovery finds them (they appear in `hermes plugins list` and the interactive `hermes plugins` UI), but none load until you explicitly enable them: ```bash hermes plugins enable disk-cleanup ``` Or via `~/.hermes/config.yaml`: ```yaml plugins: enabled: - disk-cleanup ``` This is the same mechanism user-installed plugins use. Bundled plugins are never auto-enabled — not on fresh install, not for existing users upgrading to a newer Hermes. You always opt in explicitly. To turn a bundled plugin off again: ```bash hermes plugins disable disk-cleanup # or: remove it from plugins.enabled in config.yaml ``` ## Currently shipped The repo ships these bundled plugins under `plugins/`. All are opt-in — enable them via `hermes plugins enable `. | Plugin | Kind | Purpose | |---|---|---| | `disk-cleanup` | hooks + slash command | Auto-track ephemeral files and clean them on session end | | `security-guidance` | hooks | Pattern-match dangerous code on `write_file`/`patch` and append a security warning (or block) — 25 rules (Apache-2.0 fork of Anthropic's `claude-plugins-official` patterns) | | `observability/langfuse` | hooks | Trace turns / LLM calls / tools to [Langfuse](https://langfuse.com) | | `observability/nemo_relay` | hooks | Relay observability events (turns / LLM calls / tools) to an NVIDIA NeMo endpoint | | `teams_pipeline` | standalone | Microsoft Teams meeting pipeline — Graph-backed, transcript-first meeting summaries | | `spotify` | backend (7 tools) | Native Spotify playback, queue, search, playlists, albums, library | | `google_meet` | standalone | Join Meet calls, live-caption transcription, optional realtime duplex audio | | `image_gen/openai` | image backend | OpenAI `gpt-image-2` image generation backend (alternative to FAL) | | `image_gen/openai-codex` | image backend | OpenAI image generation via Codex OAuth | | `image_gen/xai` | image backend | xAI `grok-2-image` backend | | `hermes-achievements` | dashboard tab | Steam-style collectible badges generated from your real Hermes session history | | `kanban/dashboard` | dashboard tab | Kanban board UI for the multi-agent dispatcher — tasks, comments, fan-out, board switching. See [Kanban Multi-Agent](./kanban.md). | Memory providers (`plugins/memory/*`) and context engines (`plugins/context_engine/*`) are listed separately on [Memory Providers](./memory-providers.md) — they're managed through `hermes memory` and `hermes plugins` respectively. The full per-plugin detail for the two long-running hooks-based plugins follows. ### disk-cleanup Auto-tracks and removes ephemeral files created during sessions — test scripts, temp outputs, cron logs, stale chrome profiles — without requiring the agent to remember to call a tool. **How it works:** | Hook | Behaviour | |---|---| | `post_tool_call` | When `write_file` / `terminal` / `patch` creates a file matching `test_*`, `tmp_*`, or `*.test.*` inside `HERMES_HOME` or `/tmp/hermes-*`, track it silently as `test` / `temp` / `cron-output`. | | `on_session_end` | If any test files were auto-tracked during the turn, run the safe `quick` cleanup and log a one-line summary. Stays silent otherwise. | **Deletion rules:** | Category | Threshold | Confirmation | |---|---|---| | `test` | every session end | Never | | `temp` | >7 days since tracked | Never | | `cron-output` | >14 days since tracked | Never | | empty dirs under HERMES_HOME | always | Never | | `research` | >30 days, beyond 10 newest | Always (deep only) | | `chrome-profile` | >14 days since tracked | Always (deep only) | | files >500 MB | never auto | Always (deep only) | **Slash command** — `/disk-cleanup` available in both CLI and gateway sessions: ``` /disk-cleanup status # breakdown + top-10 largest /disk-cleanup dry-run # preview without deleting /disk-cleanup quick # run safe cleanup now /disk-cleanup deep # quick + list items needing confirmation /disk-cleanup track # manual tracking /disk-cleanup forget # stop tracking (does not delete) ``` **State** — everything lives at `$HERMES_HOME/disk-cleanup/`: | File | Contents | |---|---| | `tracked.json` | Tracked paths with category, size, and timestamp | | `tracked.json.bak` | Atomic-write backup of the above | | `cleanup.log` | Append-only audit trail of every track / skip / reject / delete | **Safety** — cleanup only ever touches paths under `HERMES_HOME` or `/tmp/hermes-*`. Windows mounts (`/mnt/c/...`) are rejected. Well-known top-level state dirs (`logs/`, `memories/`, `sessions/`, `cron/`, `cache/`, `skills/`, `plugins/`, `disk-cleanup/` itself) are never removed even when empty — a fresh install does not get gutted on first session end. **Enabling:** `hermes plugins enable disk-cleanup` (or check the box in `hermes plugins`). **Disabling again:** `hermes plugins disable disk-cleanup`. ### security-guidance Fast pattern-matched security warnings on file writes. When the agent's `write_file` / `patch` / `skill_manage` calls carry content matching a known-dangerous code pattern — `pickle.load`, `yaml.load` without `SafeLoader`, `eval(`, `os.system`, `subprocess(..., shell=True)`, JS `child_process.exec`, React `dangerouslySetInnerHTML`, raw `.innerHTML =` / `.outerHTML =` / `document.write`, Node `crypto.createCipher`, AES ECB mode, TLS verification disabled, XXE-prone `xml.etree` / `minidom` parsers, `