Problem
Honeycomb lists Hermes as a harness, but the existing Hermes files are incomplete scaffolding and do not install a working Hermes Agent 0.19 adapter.
Proposed implementation
Add first-class Hermes support that:
- installs native shell hooks through
$HERMES_HOME/config.yaml;
- maps
on_session_start, pre_llm_call, post_tool_call, post_llm_call, and on_session_finalize to Honeycomb's shared lifecycle;
- captures user, completed-tool, and assistant events;
- injects synchronous model-only recall through Hermes'
{ context } response;
- registers Honeycomb's MCP server with a stable absolute Node executable;
- preserves foreign YAML, comments, hooks, MCP servers, and skills;
- fails closed on malformed YAML or a foreign
mcp_servers.honeycomb entry;
- requires Hermes' normal first-use hook consent and never edits its allowlist;
- removes only Honeycomb-owned entries/files during uninstall;
- includes deterministic, packaged-install, native-envelope, and uninstall-safety tests.
A focused pull request implementing and documenting this is ready to follow.
Problem
Honeycomb lists Hermes as a harness, but the existing Hermes files are incomplete scaffolding and do not install a working Hermes Agent 0.19 adapter.
Proposed implementation
Add first-class Hermes support that:
$HERMES_HOME/config.yaml;on_session_start,pre_llm_call,post_tool_call,post_llm_call, andon_session_finalizeto Honeycomb's shared lifecycle;{ context }response;mcp_servers.honeycombentry;A focused pull request implementing and documenting this is ready to follow.