hermes - 💡(How to fix) Fix [Bug]: `hermes dashboard` reports success even when the dashboard process exits immediately

Bug Description

Summary

Running hermes dashboard (without --no-open) prints a success message with the dashboard URL, but the underlying process exits right after. hermes dashboard --status then reports no dashboard running, and nothing is listening on the configured port.

Steps to reproduce

1. On a headless Linux VPS, run hermes dashboard (no extra flags).
2. Observe the success message:

   ╭─ ⚕ Hermes ─...
       The dashboard process is running now...
       Open it at:
       http://127.0.0.1:9119

1. Run hermes dashboard --status → No hermes dashboard processes running.
2. Run ss -tlnp | grep 9119 → no output. Nothing is bound.

Expected

Either (a) the dashboard actually stays running, or (b) the CLI reports the failure instead of printing a success message.

Actual

Success message is printed unconditionally. The process appears to be spawned and then dies (likely due to the browser-open step failing on a headless machine, since --no-open works correctly).

Workaround

hermes dashboard --no-open works as expected and the process stays alive.

Environment

• OS: Ubuntu 22.04]
• Hermes version: Hermes Agent v0.13.0 (2026.5.7)
• Python: Python 3.12.3
• Headless VPS, accessed via SSH

Steps to Reproduce

1. On a headless Linux VPS, run hermes dashboard (no extra flags).
2. Observe the success message:

   ╭─ ⚕ Hermes ─...
       The dashboard process is running now...
       Open it at:
       http://127.0.0.1:9119

1. Run hermes dashboard --status → No hermes dashboard processes running.
2. Run ss -tlnp | grep 9119 → no output. Nothing is bound.

Expected Behavior

Either (a) the dashboard actually stays running, or (b) the CLI reports the failure instead of printing a success message.

Actual Behavior

Success message is printed unconditionally. The process appears to be spawned and then dies (likely due to the browser-open step failing on a headless machine, since --no-open works correctly).

Affected Component

Tools (terminal, file ops, web, code execution, etc.)

Messaging Platform (if gateway-related)

No response

Debug Report

Sorry. Having cert issues.

Operating System

ubuntu 24.04

Python Version

3.12.3

Hermes Version

v0.13.0 (2026.5.7)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR