[CLI]: Add dashboard tunnel piping for Hermes Agent

[la14-1]

What would you like?

Hermes Agent v2026.4.13 ships a Local Web Dashboard — a browser-based UI for configuration management, session monitoring, skill browsing, and gateway management.

Spawn already has tunnel-piping infrastructure (used by OpenClaw on port 18789). We should wire Hermes into the same system so spawn run hermes automatically exposes the dashboard to the user's local browser.

What needs to change

1. packages/cli/src/shared/agent-setup.ts — Add a tunnel property to the Hermes AgentConfig with remotePort and browserUrl (similar to OpenClaw's setup). Determine the correct port Hermes serves its dashboard on.
2. packages/cli/src/shared/orchestrate.ts — Already has generic tunnel handling; just needs the Hermes tunnel config populated.
3. packages/cli/src/commands/connect.ts — Verify SSH tunnel management picks up the new Hermes tunnel automatically.
4. manifest.json — Update the Hermes agent notes to mention dashboard availability.
5. Tests — Add/update tests in packages/cli/src/__tests__/ covering the new tunnel config.

Reference

• Release: https://github.com/NousResearch/hermes-agent/releases/tag/v2026.4.13
• Dashboard features: config management, session monitoring, skill browsing, gateway management
• New env vars from release: HERMES_HOME_MODE, network.force_ipv4
• New CLI commands: hermes backup, hermes import, hermes dump, hermes debug share

Open questions

• What port does the Hermes dashboard listen on? (Need to check the release or docs)
• Should the dashboard be auto-launched by default or opt-in via an optional setup step (like YOLO mode)?

---

Filed from Slack by SPA

[la14-1]

Triaging — this is a well-scoped enhancement request. The existing tunnel infrastructure for OpenClaw provides a clear pattern to follow. Adding under-review label.

-- refactor/community-coordinator

[la14-1]

Fix in PR #3295.

-- refactor/community-coordinator

[louisgv]

Security Triage

Category: enhancement
Assessment: Dashboard tunnel piping feature for Hermes Agent. This is a well-scoped enhancement request leveraging existing OpenClaw tunnel infrastructure patterns. The fix has been implemented in PR #3295 per community-coordinator's latest comment (2026-04-14).

Recommendation: Safe for implementation. Feature adds capability without introducing new security surface (uses existing tunnel patterns). Label updated to safe-to-work.

---

-- security/issue-checker