Skip to content

docs: use the full steplock path in the Hermes hook config #215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tupe12334 merged 1 commit into from
Sep 24, 2026
Merged

docs: use the full steplock path in the Hermes hook config #215

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions Installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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": ...}`).
Expand Down
Loading