Summary
"hermes memory status" reports agentmemory as unavailable and shows AGENTMEMORY_URL / AGENTMEMORY_SECRET as missing even when the service is running and fresh Hermes sessions can successfully use the plugin.
Actual behavior
Plugin: installed ✓
Status: not available ✗
Missing:
✓ AGENTMEMORY_URL
✓ AGENTMEMORY_SECRET
text
Expected behavior
Status should reflect the real runtime state of the configured agentmemory deployment, not only the Hermes CLI process environment.
Environment
- Hermes Agent
agentmemory plugin enabled
- agentmemory service managed by systemd user unit
- agentmemory runtime config stored in
~/.agentmemory/.env
Root cause
Missing logic for setting secrets from environment variables during status checks.
Impact
- Misleading status output
- Healthy installs look broken
- Extra debugging time for a false alarm
Suggested fix
try:
req = Request(f"{base}/agentmemory/health", method="GET")
+ secret = os.environ.get("AGENTMEMORY_SECRET", "")
+ if secret:
+ req.add_header("Authorization", f"Bearer {secret}")
with urlopen(req, timeout=2):
At minimum, do not report agentmemory as unavailable when the runtime service is demonstrably reachable and fresh Hermes sessions can use it.
Summary
"hermes memory status" reports agentmemory as unavailable and shows AGENTMEMORY_URL / AGENTMEMORY_SECRET as missing even when the service is running and fresh Hermes sessions can successfully use the plugin.
Actual behavior
Plugin: installed ✓
Status: not available ✗
Missing:
✓ AGENTMEMORY_URL
✓ AGENTMEMORY_SECRET
text
Expected behavior
Status should reflect the real runtime state of the configured agentmemory deployment, not only the Hermes CLI process environment.
Environment
agentmemoryplugin enabled~/.agentmemory/.envRoot cause
Missing logic for setting secrets from environment variables during status checks.
Impact
Suggested fix
At minimum, do not report
agentmemoryas unavailable when the runtime service is demonstrably reachable and fresh Hermes sessions can use it.