Hooks for Hermes Agent?

[Galaxy-VN]

So i was love to use codebase-memory-mcp and try to integrate in hermes so it can call search/query method auto thru codebase-memory-mcp. I make a hermes plugin https://github.com/Galaxy-VN/hermes-cbm-plugin but need more test and i am not confident so see it as ref maybe? i can make a PR, Thanks!

[iandol]

Hi, looks promising, however when I tried to install (hermes plugins install rewasa/hermes-cbm-plugin) it asked for my github username and password, I assume the the rewasa repo is private and we should use the Galaxy-VN one?

[Galaxy-VN]

Yes, that was my mistake. "rewasa" was just a typo. Thanks you for notice I have updated it

[DeusData]

Thank you for building and sharing the Hermes plugin. Current main already installs a native pre_llm_call context hook, using hook-augment's Hermes dialect. Before proposing another integration, could you identify the behavior your plugin adds beyond that path? A focused gap would give us a useful design discussion. We have not reviewed your plugin, so this is not an endorsement or a request to install it.

[Galaxy-VN]

Thank you for building and sharing the Hermes plugin. Current main already installs a native pre_llm_call context hook, using hook-augment's Hermes dialect. Before proposing another integration, could you identify the behavior your plugin adds beyond that path? A focused gap would give us a useful design discussion. We have not reviewed your plugin, so this is not an endorsement or a request to install it.

Thank you for your interest in this project.

The plugin predates the native hook. When I built it, wiring codebase-memory-mcp into Hermes was fully manual, so the plugin
grew to include its own pre_llm_call hook. That hook is the smallest part: it only injects a short hint listing indexed projects
when the user's message contains code keywords. I agree it's redundant next to the native path and I'm fine removing it.

The rest is tool surface that injected context can't provide:

• 12 tools around codebase-memory-mcp (tree-sitter graph, 158 languages): structural search, call tracing, architecture
  overview, dead code, git diff impact, Cypher queries. Hermes' built-ins for this are regex search_files and raw read_file, so
  a hint alone doesn't let the model run a call graph query.
• Subagent integration: the cbm tools are added to every delegate_task subagent's default toolsets, so delegated work uses the
  graph too.
• Setup: the plugin auto-downloads the CBM binary on first use and auto-indexes the git repo on session start. That's the
  on_session_start hook, a different one.

Right now I don't have an active roadmap for it. The original problem it worked around is gone. If upstream prefers a different
shape for CBM integration, I'm fine keeping this as a third-party plugin, or contributing whatever pieces make sense upstream.