Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix Gateway should clearly reload config or warn that model changes require restart [1 pull requests]

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…

Changing ~/.hermes/config.yaml — including model.default, provider, or api_mode — does not affect a running Gateway until hermes-gateway is restarted.

In my setup, this was not obvious, and the Gateway continued using the previous configuration until restart.

Root Cause

This behavior can be confusing because changing the config file appears to succeed, but the running Gateway silently continues with the old settings until a manual restart is performed.

Fix Action

Fixed

PR fix notes

PR #13217: feat(cli): warn users to restart gateway after config changes

Description (problem / solution / changelog)

What does this PR do?

Adds a printed warning to the CLI whenever a configuration is modified, notifying the user that they must restart the Hermes Gateway for the changes to take effect. This prevents the confusion of the gateway silently continuing with old settings.

Related Issue

Fixes #13146

Type of Change

  • [ ] 🐛 Bug fix (non-breaking change that fixes an issue)
  • [ x ] ✨ New feature (non-breaking change that adds functionality)
  • 🔒 Security fix
  • 📝 Documentation update
  • ✅ Tests (adding or improving test coverage)
  • ♻️ Refactor (no behavior change)
  • 🎯 New skill (bundled or hub)

Changes Made

  • Added a printed warning message using "hermes_cli.colors" to the "set_config_value" (and "edit_config") function in "hermes_cli/config.py".

How to Test

  1. Run hermes config set agent.max_turns 100 in the terminal.
  2. Verify that the success message is immediately followed by a yellow warning: "Note: If the Hermes Gateway is currently running, you must restart it for config changes to take effect."

Checklist

Code

  • [ x ] I've read the Contributing Guide
  • [ x ] My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
  • [ x ] I searched for existing PRs to make sure this isn't a duplicate
  • [ x ] My PR contains only changes related to this fix/feature (no unrelated commits)
  • I've run pytest tests/ -q and all tests pass
  • I've added tests for my changes (required for bug fixes, strongly encouraged for features)
  • [ x ] I've tested on my platform: <!-- e.g. Ubuntu 24.04, macOS 15.2, Windows 11 -->

Documentation & Housekeeping

<!-- Check all that apply. It's OK to check "N/A" if a category doesn't apply to your change. -->
  • I've updated relevant documentation (README, docs/, docstrings) — or N/A
  • I've updated cli-config.yaml.example if I added/changed config keys — or N/A
  • I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
  • I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
  • I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Screenshots / Logs

<img width="744" height="49" alt="Screenshot 2026-04-21 at 01 43 29" src="https://github.com/user-attachments/assets/b998c518-c385-4bd5-9bd4-03580f27ea9b" />

Changed files

  • hermes_cli/config.py (modified, +2/-0)
RAW_BUFFERClick to expand / collapse

Summary

Changing ~/.hermes/config.yaml — including model.default, provider, or api_mode — does not affect a running Gateway until hermes-gateway is restarted.

In my setup, this was not obvious, and the Gateway continued using the previous configuration until restart.

Steps to reproduce

  1. Start hermes-gateway.
  2. Edit ~/.hermes/config.yaml and change model.default or api_mode.
  3. Do not restart the Gateway.
  4. Observe that the running Gateway continues using the old configuration.

Expected behavior

One of the following should happen:

  • The Gateway hot-reloads the relevant configuration, or
  • The Gateway clearly logs or warns that a restart is required for config changes to take effect.

Actual behavior

The running Gateway keeps using the previous configuration until it is restarted.

Environment

  • OS: Linux Mint
  • Gateway execution mode: systemd --user
  • Config file: ~/.hermes/config.yaml

Notes

This behavior can be confusing because changing the config file appears to succeed, but the running Gateway silently continues with the old settings until a manual restart is performed.

extent analysis

TL;DR

Restarting the hermes-gateway service is likely necessary for configuration changes in ~/.hermes/config.yaml to take effect.

Guidance

  • Verify that the hermes-gateway service is properly configured to reload its configuration, if supported.
  • Check the Gateway's documentation for any specific instructions on how to apply configuration changes without restarting.
  • Consider adding a logging or warning mechanism to inform users that a restart is required for configuration changes to take effect.
  • Test the behavior with different configuration changes to ensure the issue is not specific to certain settings.

Example

No code snippet is provided as the issue does not imply a code-based solution.

Notes

The current behavior may be due to the Gateway's design or a limitation in its configuration reloading mechanism. Further investigation into the Gateway's documentation or source code may be necessary to determine the root cause.

Recommendation

Apply workaround: Restart the hermes-gateway service after making changes to ~/.hermes/config.yaml, as this is the currently known method to ensure configuration changes take effect.

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…

FAQ

Expected behavior

One of the following should happen:

  • The Gateway hot-reloads the relevant configuration, or
  • The Gateway clearly logs or warns that a restart is required for config changes to take effect.
#api#ssr#installation#tensor shape#autograd error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING