Built-in Plugins
Hermes ships a small set of plugins bundled with the repository. They live under and load automatically alongside user installed plugins in . They use the same
- Section
- Core Features
- Source
- hermesbible.com/docs/user-guide/features/built-in-plugins
Hermes ships a small set of plugins bundled with the repository. They live under and load automatically alongside user installed plugins in . They use the same
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- How discovery works
- Bundled plugins are opt-in
- Currently shipped
- disk-cleanup
- security-guidance
- observability/langfuse
- google_meet
- hermes-achievements
- Adding a bundled plugin
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
Section map
How discovery works
Maps how discovery works to the Core Features documentation path, with the source page reserved for exact commands and updates.
Bundled plugins are opt-in
Maps bundled plugins are opt-in to the Core Features documentation path, with the source page reserved for exact commands and updates.
Currently shipped
Maps currently shipped to the Core Features documentation path, with the source page reserved for exact commands and updates.
disk-cleanup
Maps disk-cleanup to the Core Features documentation path, with the source page reserved for exact commands and updates.
security-guidance
Maps security-guidance to the Core Features documentation path, with the source page reserved for exact commands and updates.
observability/langfuse
Maps observability/langfuse to the Core Features documentation path, with the source page reserved for exact commands and updates.
google_meet
Maps google_meet to the Core Features documentation path, with the source page reserved for exact commands and updates.
hermes-achievements
Maps hermes-achievements to the Core Features documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
- Primary decision areas: How discovery works, Bundled plugins are opt-in, Currently shipped, disk-cleanup, security-guidance. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: built-in, plugins, ships, small, bundled. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for built-in plugins before applying exact upstream commands.
Open the source anchor for How discovery works and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
- Start with the source section for How discovery works; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for Bundled plugins are opt-in if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Use the upstream source page for exact current behavior before applying configuration changes.
What this page covers
- Core concept and where it fits in the Hermes Agent system.
- Setup or operating context implied by the upstream page summary.
- The source page link for full current details and updates.
Source mirror note
This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.
Open source page