docs/tests: add Hermes + OMNI integration best practices#95
Merged
Conversation
…ering via new signal definitions
…cs and optimized plugin hooks
…red schema including transformation rules and unit tests
…ure and document autonomous MCP tool integration
…ops with OMNI MCP tools
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/HERMES_OMNI_INTEGRATION.mdwith prerequisites, install, verification, tuning, pitfalls, decision tree, and ops checklist for Hermes + OMNI.src/agents/hermes.rstests to cover Hermes default config and command patterns.README.mdwith a link to the new integration guide.Validation
cargo test --lib agents::hermes::testspassed (7/7).cargo test --libpassed (357/357).Related
feat/hermes-updateintegration; this branch focuses on operational best practices.PR Auto Describe
Summary
Added first-class Hermes Agent integration with automated setup (
omni init --hermes), comprehensive documentation, and native OMNI MCP tools for autonomous loops. The integration now auto-registers the MCP server, enables Hermes compression, and surfaces startup validation warnings directly into the Hermes system prompt for self-healing.Key Changes
omni init --hermesfully automated — installs plugin, registers MCP server, enables compression, writes Hermes-optimized OMNI config (no manual steps)validate_startup()function checks MCP registration, compression, plugin files, and OMNI config; injects warnings into HermessystemPromptAdditionctx.compact()when OMNI emits pressure warningssignals/tools/hermes.toml) — strips Hermes tool wrappers, headers, separatorsHERMES_OMNI_INTEGRATION.md(setup, verification, best practices, pitfalls) andhermes-loop.md(Maker-Checker pattern)Detailed Breakdown
Integration (
src/agents/hermes.rs)validate_startup()systemPromptAdditionconfigured_compression()compression.enabled: truein Hermes confighermes_default_config()mode="efficient", all distillations on, pinned files (AGENTS.md, .omni/CONTEXT.md)hermes_command_patterns()install()enhanced:~/.hermes/config.yamlthreshold: 0.50,target_ratio: 0.20)[agents.hermes]section to~/.omni/config.tomlwithout overwritingdoctor_check()enhanced:install()to repair all gaps[agents.hermes]sectionPython plugin (
__init__.py) enhanced:on_post_tool_callchecks stdout for[omni:context pressure: WARNING/CRITICAL]→ callsctx.compact()OMNI_LOOP_ID,OMNI_LOOP_GOAL,OMNI_LOOP_BUDGETenv varsHooks (
src/hooks/session_start.rs)validate_startup()whenagent_id == "hermes"system_prompt_additionso agent sees them without extra commandsSignals (
signals/tools/hermes.toml)match_command:terminal,read_file,web_search,browser_*,execute_code,delegate_taskterm:,>,Tool Result,Hermes Gateway)Notes
plugins:block; falls back to EOF if not foundBreaking Changes
None. All changes are additive or modify only new integration scaffolding. Existing OMNI behavior and configs are preserved.
Last updated: 2026-06-15 04:39:23