hermes-client-web-ui

Provides a web chat interface for Hermes Agent with multi-profile management and SSE streaming.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill hermes-client-web-ui-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-client-web-ui
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/hermes-client-web-ui
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill hermes-client-web-ui-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing multiple Hermes Agent profiles and conversations from the command line is fragmented; this Skill sets up a browser-based dashboard that unifies profile management, streaming chat, and terminal access in one place. ## Core Features & Use Cases - Multi-Profile Management: Create, list, and delete Hermes profiles as separate UI agents, each mapped 1:1 to a Hermes home directory, config, and sessions. - Streaming Chat via SSE: Every chat turn spawns hermes -p <profile> chat and streams stdout to the browser over Server-Sent Events, with file upload support passed to Hermes by absolute path. - Session Sync & Interactive Terminal: Sessions started in the standalone Hermes REPL auto-appear in the sidebar via filesystem watching, and an xterm.js PTY over WebSocket handles interactive commands like model configuration. - Use Case: A developer runs several Hermes profiles for different projects, starts a conversation in the terminal, then continues it in the browser at http://localhost:18888 with full history synced from ~/.hermes/profiles/*/sessions/*.json. ## Quick Start Set up the Hermes Client web dashboard by cloning the repository, running npm start, and logging in at localhost:18888 to manage my Hermes agent profiles.

Frequently Asked Questions about hermes-client-web-ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the Hermes Client web interface?▼

Clone the hermes_client repository, run npm start, and the script builds the app, deploys to ~/.hermes_client, and installs auto-start. The client runs at http://localhost:18888 with default credentials [email protected] / 123456.

How does Hermes Client stream chat responses in the browser?▼

Each chat turn spawns `hermes -p <profile> chat -Q -q "<message>"` and streams stdout over Server-Sent Events. The client reads the response body with a reader loop, parsing `data:` lines until the `[DONE]` sentinel.

Can I manage multiple Hermes agent profiles in one dashboard?▼

Yes, each UI agent maps 1:1 to a Hermes profile with its own home directory, config, and sessions. Create or delete profiles via the /api/agents endpoints, which run `hermes profile add` and `hermes profile delete`.

Does Hermes Client sync terminal sessions with the web UI?▼

Yes, the backend watches ~/.hermes/profiles/<profile>/sessions/*.json and inserts changes into SQLite. Sessions started in the standalone hermes REPL appear in the sidebar automatically, and web conversations can be resumed with `hermes chat -r <key>`.

Why is the Hermes binary not found by the API server?▼

The API checks PATH plus common locations like ~/.local/bin/hermes and /opt/homebrew/bin/hermes. If hermes is elsewhere, set HERMES_BIN=/path/to/hermes in api/.env and restart with hermes_client restart.

How do I fix CORS issues when accessing Hermes Client remotely?▼

Edit ~/.hermes_client/api/.env to set ALLOWED_DOMAIN with your LAN or Tailscale addresses and enable HERMES_STRICT_CORS=1. Then run hermes_client restart to apply the allowlist.