Skip to content

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

Merged
tupe12334 merged 1 commit into
mainfrom
docs/hermes-absolute-path
Sep 24, 2026
Merged

tupe12334 merged 1 commit into
mainfrom
docs/hermes-absolute-path

Conversation

@tupe12334

Copy link
Copy Markdown
Member

Summary

While testing the published steplock 0.1.0 (cargo install steplock) with Hermes v0.21.4, hermes hooks doctor reported ✗ script missing or not executable for the documented command: "steplock". The hook itself fires correctly: Hermes resolves bare commands on PATH at runtime, but the doctor doesn't. With command: "~/.cargo/bin/steplock" the doctor shows ✓ script exists and is executable.

  • Installation.md: the Hermes example uses ~/.cargo/bin/steplock (Hermes expands ~) and explains why.

Test plan

  • hermes hooks doctor with the bare name: ✗ script missing; with the full path: ✓ script exists and is executable
  • hermes hooks test pre_tool_call with the full path blocks, then approves after two ack.sh runs

🤖 Generated with Claude Code

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) <noreply@anthropic.com>
@tupe12334
tupe12334 marked this pull request as ready for review September 24, 2026 11:20
@tupe12334
tupe12334 merged commit d70343d into main Sep 24, 2026
13 checks passed
@tupe12334
tupe12334 deleted the docs/hermes-absolute-path branch September 24, 2026 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant