Context Engine Plugins
Building a Context Engine Plugin Context engine plugins replace the built in with an alternative strategy for managing conversation context. For example, a Loss
- Section
- Developer Guide
- Source
- hermesbible.com/docs/developer-guide/context-engine-plugin
Building a Context Engine Plugin Context engine plugins replace the built in with an alternative strategy for managing conversation context. For example, a Loss
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- How it works
- Directory structure
- The ContextEngine ABC
- Class attributes your engine must maintain
- Optional methods
- Engine tools
- Registration
- Via directory (recommended)
- Via general plugin system
- Lifecycle
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 it works
Maps how it works to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Directory structure
Maps directory structure to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
The ContextEngine ABC
Maps the contextengine abc to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Class attributes your engine must maintain
Maps class attributes your engine must maintain to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Optional methods
Maps optional methods to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Engine tools
Maps engine tools to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Registration
Maps registration to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Via directory (recommended)
Maps via directory (recommended) to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Developer Guide 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 it works, Directory structure, The ContextEngine ABC, Class attributes your engine must maintain, Optional methods. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: context, engine, plugins, building, plugin. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for context engine plugins before applying exact upstream commands.
Open the source anchor for How it 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 Developer Guide, then open the linked source page for exact current syntax.
- Start with the source section for How it 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 Directory structure 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