BjxdZddlZddlZddlZddlmZmZmZm Z m Z ddl Z ddl m Z e dz ZGddZy)a Event Hook System A lightweight event-driven system that fires handlers at key lifecycle points. Hooks are discovered from ~/.hermes/hooks/ directories, each containing: - HOOK.yaml (metadata: name, description, events list) - handler.py (Python handler with async def handle(event_type, context)) Events: - gateway:startup -- Gateway process starts - session:start -- New session created (first message of a new session) - session:end -- Session ends (user ran /new or /reset) - session:reset -- Session reset completed (new session entry created) - agent:start -- Agent begins processing a message - agent:step -- Each turn in the tool-calling loop - agent:end -- Agent finishes processing - command:* -- Any slash command executed (wildcard match) Errors in hooks are caught and logged but never block the main pipeline. N)AnyCallableDictListOptional)get_hermes_homehooksceZdZdZdZedeefdZd dZ d dZ de dee fd Z dde d eee efddfd Z dde d eee efdeefd Zy) HookRegistryz Discovers, loads, and fires event hooks. Usage: registry = HookRegistry() registry.discover_and_load() await registry.emit("agent:start", {"platform": "telegram", ...}) c i|_g|_yN) _handlers _loaded_hooksselfs 2/home/ubuntu/.hermes/hermes-agent/gateway/hooks.py__init__zHookRegistry.__init__-s46)+returnc,t|jS)z'Return metadata about all loaded hooks.)listrrs r loaded_hookszHookRegistry.loaded_hooks2sD&&''rNcy)uRegister built-in hooks that are always active. Currently empty — no shipped built-in hooks. Kept as the extension point for future always-on gateway hooks so they drop in without re-plumbing discover_and_load(). Nrs r_register_builtin_hooksz$HookRegistry._register_builtin_hooks7s rc f|jtjsyttj D] }|j s|dz }|dz }|jr|js@ t j|jd}|rt|tstd|jdd |jd |j}|jd g}|std|d d d |}tjj!||}| |j"td|dd tjj%|} | t&j(|< |j"j+| t1| dd} | td|dd |D]-} |j2j5| gj7| /|j8j7||jdd|t;|dtd|d|d  y#t,$r"t&j(j/|dwxYw#t,$r(} td|jd| d Yd} ~ hd} ~ wwxYw)aI Scan the hooks directory for hook directories and load their handlers. Also registers built-in hooks that are always active. Each hook directory must contain: - HOOK.yaml with at least 'name' and 'events' keys - handler.py with a top-level 'handle' function (sync or async) Nz HOOK.yamlz handler.pyzutf-8)encodingz[hooks] Skipping z: invalid HOOK.yamlTflushnameeventsz: no events declared hermes_hook_z: could not load handler.pyhandlez: no 'handle' function found description)r r$r!pathz[hooks] Loaded hook 'z' for events: zooks] Error loading hook z: )r HOOKS_DIRexistssortediterdiris_diryaml safe_load read_text isinstancedictprintr get importlibutilspec_from_file_locationloadermodule_from_specsysmodules exec_module Exceptionpopgetattrr setdefaultappendrstr) rhook_dir manifest_path handler_pathmanifest hook_namer! module_namespecmodule handle_fneventes rdiscover_and_loadzHookRegistry.discover_and_load@s $$&! y0023@ VH??$${2M#l2L '')1D1D1F6 V>>-*A*A7*A*STz(D'A-hmm_+1 K(KK++F3 $FHd; $-i[8TU]ab$KENN--eR8?? JK""))%#+<< r#B$M +-i[vhOW[\{@ VR!KKOOK6, V3HMM?"QCHPTUU VsLAI?AI?AI?2I?I- I?A>I?+I<<I?? J0J++J0 event_typect|jj|g}d|vrD|jdd}|d}|j |jj|g|S)zReturn all handlers that should fire for ``event_type``. Exact matches fire first, followed by wildcard matches (e.g. ``command:*`` matches ``command:reset``). :rz:*)rrr2splitextend)rrMhandlersbase wildcard_keys r_resolve_handlerszHookRegistry._resolve_handlerssi **:r:; * ##C(+D"V2;L OODNN..|R@ ArcontextcK|i}|j|D]+} |||}tj|r |d{-y7#t$r}t d|d|dYd}~Rd}~wwxYww)a Fire all handlers registered for an event, discarding return values. Supports wildcard matching: handlers registered for "command:*" will fire for any "command:..." event. Handlers registered for a base type like "agent" won't fire for "agent:start" -- only exact matches and explicit wildcards. Args: event_type: The event identifier (e.g. "agent:start"). context: Optional dict with event-specific data. N[hooks] Error in handler for '': Tr)rUasyncio iscoroutiner;r1)rrMrVfnresultrKs remitzHookRegistry.emits ?G((4 WB WJ0&&v. LL  W ! W6zl#aSIQUVV Ws?A2#A AA A2A  A/A*%A2*A//A2cK|i}g}|j|D]>} |||}tj|r |d{}||j|@|S7#t$r}t d|d|dYd}~fd}~wwxYww)aFire handlers and return their non-None return values in order. Like :meth:`emit` but captures each handler's return value. Used for decision-style hooks (e.g. ``command:`` policies that want to allow/deny/rewrite the command before normal dispatch). Exceptions from individual handlers are logged but do not abort the remaining handlers. NrXrYTr)rUrZr[r?r;r1)rrMrVresultsr\r]rKs r emit_collectzHookRegistry.emit_collects ?G((4 WB WJ0&&v.#)\F%NN6*  W * W6zl#aSIQUVV Ws@B#AAABA B(B;BBB)rNr )__name__ __module__ __qualname____doc__rpropertyrr0rrrLr@rrUrrrr^rarrrr r #s, (d4j((OVb C DN WSW8DcN3KWW[W8-1$sCx.) c rr )rerZimportlib.utilr3r8typingrrrrrr,hermes_cli.configrr'r rrrrjs<* 66 -   ' oor