From bd35200ec54f4b294fcb58aa5dbb3ef195b9e808 Mon Sep 17 00:00:00 2001 From: Ofek Gabay Date: Thu, 24 Sep 2026 14:18:12 +0300 Subject: [PATCH] docs: use the full steplock path in the Hermes hook config hermes hooks doctor does not resolve bare commands on PATH and reports "script missing or not executable" for command: steplock, although the hook runs fine. Found while testing the published 0.1.0 with Hermes v0.21.4. Co-Authored-By: Claude Opus 5.5 (1M context) --- Installation.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Installation.md b/Installation.md index 81c32fb..f4f34c5 100644 --- a/Installation.md +++ b/Installation.md @@ -159,13 +159,15 @@ In `~/.hermes/config.yaml`: hooks: pre_tool_call: - matcher: "terminal" - command: "steplock" + command: "~/.cargo/bin/steplock" timeout: 10 on_session_end: - - command: "steplock" + - command: "~/.cargo/bin/steplock" timeout: 10 ``` +Use the full path to the binary (`which steplock`; `~/.cargo/bin/steplock` after `cargo install`). Hermes finds a bare `steplock` on `PATH` at runtime, but `hermes hooks doctor` does not search `PATH` and reports `script missing or not executable`. + - `pre_tool_call` with `matcher: "terminal"` gates shell commands. polyhook maps Hermes `terminal` to `bash`, so checklists with `on_tool = "bash"` work unchanged. - `on_session_end` removes the session state when the Hermes session ends. - steplock answers in Hermes's own format (`{"action": "block", "message": ...}`).