hermes - 💡(How to fix) Fix [BUG] Gateway not auto-restarted after `hermes update`

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…

Code Example

2026-05-23 23:44:49 INFO gateway.run: Stopping gateway for restart...
2026-05-23 23:44:53 INFO gateway.run: Gateway stopped (total teardown 3.25s)
# [NO RESTART EVENT AFTER THIS]
RAW_BUFFERClick to expand / collapse

Bug Description

After running hermes update, the gateway (launchd service) is stopped cleanly (Exit 15) but never automatically restarted. The gateway stays DOWN until manually started via hermes gateway restart.

Steps to Reproduce

  1. Hermes Agent running with active gateway (e.g., Telegram connection established)
  2. Run hermes update
  3. Update installs and gracefully stops the old gateway (Exit 15 / SIGTERM)
  4. New gateway is NEVER started automatically
  5. Result: Gateway is DOWN, no platform connections

Expected Behavior

The gateway should automatically restart after a successful update (via launchd).

Actual Behavior

  • Main gateway stops cleanly with Exit 15 (SIGTERM / graceful shutdown)
  • NO auto-start event after update
  • Gateway stays DOWN until manual restart
  • Log excerpt:
2026-05-23 23:44:49 INFO gateway.run: Stopping gateway for restart...
2026-05-23 23:44:53 INFO gateway.run: Gateway stopped (total teardown 3.25s)
# [NO RESTART EVENT AFTER THIS]

Environment

  • OS: macOS 26.5 (Sequoia)
  • Hermes Agent: v0.14.0 (2026.5.16)
  • Python: 3.11.15
  • Gateway Manager: launchd
  • Launchd plist: ~/Library/LaunchAgents/ai.hermes.gateway.plist

Impact

Users without direct terminal access lose ALL gateway connections after an update. Critical when triggered via /update from within the gateway.

Suggested Fix

After successful update, add: launchctl kickstart gui/$(id -u) ai.hermes.gateway or spawn background hermes gateway restart.

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…

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 [BUG] Gateway not auto-restarted after `hermes update`