Gateway hooks: agent:end event never dispatches to handler

Environment

• Hermes Agent v0.10.0 (2026.4.16)
• Python 3.11.15
• macOS 15.7.5 (Intel x86_64)
• Gateway running via hermes gateway run --replace
• Model: moonshotai/kimi-k2.6 via OpenRouter

Description

A gateway hook subscribed to agent:end loads successfully but the handle() function is never called. Messages are processed and responses delivered correctly — the hook simply never fires.

Steps to Reproduce

1. Create hook directory and files:

~/.hermes/hooks/circuit-breaker/HOOK.yaml
~/.hermes/hooks/circuit-breaker/handler.py

1. HOOK.yaml:

name: circuit-breaker
description: Log dispatches to SQLite
events:
  - agent:end

1. handler.py (minimal reproducer):

import logging
from pathlib import Path

LOG = Path.home() / "spock" / "logs" / "hook-test.log"

async def handle(event_type, context):
    logging.basicConfig(filename=str(LOG), level=logging.DEBUG)
    logging.debug(f"HOOK FIRED: {event_type} keys={list(context.keys())}")
    with open(str(LOG), "a") as f:
        f.write(f"FIRED: {event_type}\n")

1. Start gateway: hermes gateway run --replace
2. Gateway log confirms hook loaded:

[hooks] Loaded hook 'circuit-breaker' for events: ['agent:end']

1. Send a message via Telegram (or Signal). Agent responds correctly.
2. Check ~/spock/logs/hook-test.log — file does not exist. handle() was never called.

Expected Behaviour

After the agent finishes processing a message and sends its response, the agent:end event should dispatch to all registered gateway hooks, calling handle("agent:end", context) with the documented context keys (platform, user_id, session_id, message, response).

Actual Behaviour

Hook loads and registers without error. Agent processes messages normally. handle() is never invoked. No errors in gateway.log or gateway.error.log related to hook dispatch. The handler imports cleanly outside the gateway process (python3 -c "import handler" succeeds).

Observations

• The hook loads on every gateway restart (confirmed by repeated [hooks] Loaded hook log lines)
• The handler module is syntactically valid and importable
• The handler function signature matches the documented interface (async def handle(event_type, context))
• Other gateway functionality works correctly (Telegram/Signal message processing, slash commands, pairing)
• No exception or error logged at dispatch time — suggesting the dispatch call site itself is not reached, rather than the handler failing silently

Questions

1. Is agent:end actually wired to dispatch in gateway mode, or only in CLI chat mode?
2. Is there a different event name for gateway-processed messages (e.g. gateway:agent:end or message:end)?
3. Does the hook system require hooks_auto_accept: true in config.yaml for gateway hooks to fire, even after loading?

Workaround

None found. Considering polling OpenRouter's usage API as an alternative data source for dispatch logging.