Skip to content

[Bug] "hermes memory status" reports agentmemory as unavailable despite active service #520

Description

@Mavis2103

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions