Plugin System

源码版本v2026.7.20

Responsibility

Plugins are Hermes's extension skeleton: provider profiles, platform adapters, context engine, cron providers, memory backends, browser, image/video generation... all plug in through the plugin mechanism. plugins/ provides PluginContext (the registration entry) + utility functions; each plugin subdirectory is self-contained by domain. It coordinates with ToolRegistry/PlatformRegistry: plugins only "declare and register"; the registries handle "lookup and dispatch".

Key Files

• plugins/__init__.py — PluginContext, registration entries (register_platform, register_provider, etc.)
• plugin_utils.py — shared plugin utility functions
• model-providers/ — LLM provider profiles (see Providers)
• platforms/ — Telegram/Discord/Slack platform adapters (see Platform Adapters)
• context_engine/ — context engine extensions
• cron_providers/ — cron scheduling backends
• memory/ — memory backends
• browser/ / web/ — browser and web capabilities
• image_gen/ / video_gen/ — multimodal generation
• observability/ / security-guidance/ — observability and security

Data Flow

1. At startup, init_agent (agent/agent_init.py:276) triggers plugin discovery.
2. Each plugin subdirectory is imported; module-level code calls PluginContext registration methods:
   • model-provider → register_provider:53
   • platform → platform_registry.register:231
   • tool → registry.register:365 (via namespace policy)
3. The registries (singletons) become the lookup truth; the main loop and gateway only read the registries and do not directly depend on specific plugins.
4. Plugins are hot-pluggable: unloading is just unregister; the registry handles priority and overrides.

Summary

Plugin = "subdirectory + registration". All cross-cutting capabilities (providers, platforms, tools, memory, cron, multimodal) go through the same registration skeleton, so the core loop stays stable. Adding a capability = creating a plugin subdirectory and registering; no need to touch the agent's trunk.