Evidence record / hermes-agent

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the signals and issues that cite it, below.

v0.15.1 Patch Release - Dashboard reload loop hotfix and Docker hardening

What Changed

Critical fix for dashboard infinite-reload loop in loopback mode (Docker, hosted instances); Docker dashboard now requires explicit HERMES_DASHBOARD_INSECURE=1 env var instead of inferring from bind host; MCP bare commands (npx, npm, node) resolve correctly in Docker; Kanban worker SIGTERM termination restored; Skills catalog expanded from 858 to 19,932 entries via sitemap; URL redaction passthrough fixed.

Operator Implication

Critical for Docker deployments: explicit HERMES_DASHBOARD_INSECURE=1 required for insecure binding; existing setups must update env configuration. Dashboard reload loop fix essential for loopback-mode deployments (Docker, hosted instances). MCP command resolution fix improves container compatibility.

Receipt

Release notes highlight: ‘Dashboard 401 reload loop fixed — In loopback mode the dashboard’s identity probe (/api/auth/me) returns 401 by design, but v0.15.0’

Finding metadata

Confidence: high
Actionability: observe
Accessibility impact: medium

Run: 2026-06-03-weekly-digest-2026-05-28_2026-06-03-frontier-v0

Finding ID: 2026-05-29-hermes-agent-patch-release

Accepted signals

Docker dashboard insecure binding now requires explicit HERMES_DASHBOARD_INSECURE=1 opt-in / 2026-06-03

Profile citations

Hermes Agent / claim / v0-15-multi-agent-and-docker-optin

Source links

Primary links, including exact changelog lines when available.

Hermes Agent
release noteRelease notes highlight: 'Dashboard 401 reload loop fixed — In loopback mode the dashboard's identity probe (`/api/auth/me`) returns 401 by design, but v0.15.0's stale-token reload guard treated everyNousResearch/hermes-agent / v2026.5.29

Versioned source: run artifact