Skip to content

The agent that grows with you

chore(catalog): state the update-lock probe's writable open exactly

Iko9e6bade82596
diff --git a/plugin-catalog/hermes-guide.yaml b/plugin-catalog/hermes-guide.yaml
index 6343757a174..7e8b1d92c84 100644
--- a/plugin-catalog/hermes-guide.yaml
+++ b/plugin-catalog/hermes-guide.yaml
@@ -1,7 +1,7 @@
name: hermes-guide
repo: https://github.com/iap/hermes-guide
sha: 7dbc6c8b949b33c56faff1eddd07572f47c46e29
-description: "Read-only diagnostics for Hermes configuration: /hermes-doctor in-session and hermes guide in a terminal. Nine read-only health checks (config, mcp, skills, commands, hooks, plugins, memories, sessions, update) and points to 22 troubleshooting skills, installed separately as a skills tap, for what the built-in doctor doesn't cover. Complements — never replaces — hermes doctor. Disclosure — reads config.yaml, SKILL.md frontmatter, skill bundles, plugin manifests, the shell-hooks allowlist and the built-in MEMORY.md/USER.md stores read-only (the report quotes short memory snippets); the sessions scope reads the tail of logs/agent.log read-only for runaway-session signatures (session ids, model names and token counts appear in the report); the update scope reads the update-lock record in the co-located hermes-agent checkout under $HERMES_HOME and probes it — owner-PID liveness, then a brief lock acquisition it releases immediately, opening the lock file writable where the platform requires it (writes no content, never deletes the lock); registers one read-only plugin skill, hermes-guide:start, listed in model sessions while the plugin is enabled; /hermes-doctor and hermes guide run hermes config path and hermes hooks doctor as subprocesses (argument list, no shell), and hermes hooks doctor executes every approved shell hook once with a synthetic payload; with opt-in proactive: true it runs the checks (including the agent.log scan) in-process at each session start/end (no hooks executed) and once per process runs git ls-remote against the plugin's GitHub repo to log a newer-release notice (no download, no local writes). The 22 troubleshooting skills are not loaded by the plugin: they install separately from the repo as a skills tap, which this entry's pin does not cover."
+description: "Read-only diagnostics for Hermes configuration: /hermes-doctor in-session and hermes guide in a terminal. Nine read-only health checks (config, mcp, skills, commands, hooks, plugins, memories, sessions, update) and points to 22 troubleshooting skills, installed separately as a skills tap, for what the built-in doctor doesn't cover. Complements — never replaces — hermes doctor. Disclosure — reads config.yaml, SKILL.md frontmatter, skill bundles, plugin manifests, the shell-hooks allowlist and the built-in MEMORY.md/USER.md stores read-only (the report quotes short memory snippets); the sessions scope reads the tail of logs/agent.log read-only for runaway-session signatures (session ids, model names and token counts appear in the report); the update scope reads the update-lock record in the co-located hermes-agent checkout under $HERMES_HOME and probes it — owner-PID liveness, then a brief lock acquisition it releases immediately, opening the lock file writable, with a read-only fallback for a root-owned lock on POSIX (writes no content, never deletes the lock); registers one read-only plugin skill, hermes-guide:start, listed in model sessions while the plugin is enabled; /hermes-doctor and hermes guide run hermes config path and hermes hooks doctor as subprocesses (argument list, no shell), and hermes hooks doctor executes every approved shell hook once with a synthetic payload; with opt-in proactive: true it runs the checks (including the agent.log scan) in-process at each session start/end (no hooks executed) and once per process runs git ls-remote against the plugin's GitHub repo to log a newer-release notice (no download, no local writes). The 22 troubleshooting skills are not loaded by the plugin: they install separately from the repo as a skills tap, which this entry's pin does not cover."
maintainer: iap
tier: community
category: tools