Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix workflow-enforcement plugin stops loading after gateway restart [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#12868•Fetched 2026-04-20 12:16:32
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Author
evanbongevanbong
Participants
evanbongevanbong
Timeline (top)
closed ×1commented ×1

The custom plugin at was registering its hook successfully at 06:00-06:15 SGT, but stopped being discovered after a gateway restart around 06:22.

Error Message

  1. The plugin failing may affect discovery order or error handling

Root Cause

The custom plugin at was registering its hook successfully at 06:00-06:15 SGT, but stopped being discovered after a gateway restart around 06:22.

Fix Action

Fix / Workaround

  • Plugin file exists: 235 lines at ~/.hermes/plugins/workflow-enforcement/__init__.py
  • All three safety features present (HERMES_NO_ENFORCE kill switch, ALLOWED_REPOS allowlist, GUARDED_TOOLS = {write_file, patch})
  • Plugin was loading correctly before the 06:22 gateway session
  • Zero mentions of 'workflow-enforcement' in logs after 06:15:55

Without the plugin, write_file and patch are no longer blocked in git repos. Workflow enforcement (Beads check, GitHub issue gate) is offline.

Code Example

06:00:14  Plugin discovery: 2 found, 1 enabled
  - git-workflow: FAILED (register_command bad 'help' kwarg)
  - workflow-enforcement: loaded OK, registered pre_tool_call hook

06:15:42  Plugin discovery: 2 found, 1 enabled (still working)

06:15:55  Plugin discovery: 2 found, 1 enabled (still working)

06:22:48  Plugin discovery: 1 found, 0 enabled  ← REGRESSION
  - git-workflow: still failing
  - workflow-enforcement: no longer discovered

06:30:30  Plugin discovery: 1 found, 0 enabled (still broken)
RAW_BUFFERClick to expand / collapse

Summary

The custom plugin at was registering its hook successfully at 06:00-06:15 SGT, but stopped being discovered after a gateway restart around 06:22.

Timeline (April 20, 2026)

06:00:14  Plugin discovery: 2 found, 1 enabled
  - git-workflow: FAILED (register_command bad 'help' kwarg)
  - workflow-enforcement: loaded OK, registered pre_tool_call hook

06:15:42  Plugin discovery: 2 found, 1 enabled (still working)

06:15:55  Plugin discovery: 2 found, 1 enabled (still working)

06:22:48  Plugin discovery: 1 found, 0 enabled  ← REGRESSION
  - git-workflow: still failing
  - workflow-enforcement: no longer discovered

06:30:30  Plugin discovery: 1 found, 0 enabled (still broken)

Evidence

  • Plugin file exists: 235 lines at ~/.hermes/plugins/workflow-enforcement/__init__.py
  • All three safety features present (HERMES_NO_ENFORCE kill switch, ALLOWED_REPOS allowlist, GUARDED_TOOLS = {write_file, patch})
  • Plugin was loading correctly before the 06:22 gateway session
  • Zero mentions of 'workflow-enforcement' in logs after 06:15:55

Plugin Discovery Path

Hermes looks in ~/.hermes/plugins/ for plugins. The directory exists there.

Hypotheses

  1. Gateway restart at 06:22 cleared the plugin state and something in plugin discovery changed
  2. Plugin directory may have been touched/modified between sessions
  3. The plugin failing may affect discovery order or error handling

Impact

Without the plugin, write_file and patch are no longer blocked in git repos. Workflow enforcement (Beads check, GitHub issue gate) is offline.

extent analysis

TL;DR

The plugin discovery issue may be resolved by investigating the plugin directory and its contents after the gateway restart, focusing on potential changes or issues with the workflow-enforcement plugin.

Guidance

  • Verify the plugin directory ~/.hermes/plugins/ and its contents, especially the workflow-enforcement plugin, for any changes or issues after the gateway restart at 06:22.
  • Check the logs for any errors or warnings related to plugin discovery after 06:15:55 to identify potential issues.
  • Investigate if the git-workflow plugin's failure is affecting the discovery of other plugins, including workflow-enforcement.
  • Review the plugin discovery mechanism to ensure it is correctly handling plugin registration and discovery after a gateway restart.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue may be related to the gateway restart or changes to the plugin directory, but further investigation is needed to determine the root cause. The git-workflow plugin's failure may also be a contributing factor.

Recommendation

Apply a workaround by manually reloading the workflow-enforcement plugin after the gateway restart to ensure it is registered and functional, while investigating the root cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#network issue#logging issue#authentication issue#prompt issue#agent setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix workflow-enforcement plugin stops loading after gateway restart [1 comments, 1 participants]