Which Hermes Interface Fits Your Operator Tasks?

Use the official Hermes Dashboard for installation administration. Trial Hermes Workspace for workflows that move between sessions, files, and a terminal. Time both against the same observable completion criteria.

Match the session to the intended profile

Give each test profile a distinct synthetic session title, such as Cedar Invoice Check and Maple Invoice Check. Open the official Hermes Dashboard using its documented loopback default and have a second operator locate the Cedar session and record one visible session attribute. If you operate named profiles, repeat the task with the documented isolated dashboard option and verify which profile’s session appears. Time the task from opening the interface to recording the evidence. A correct-looking session from the wrong profile is a failed trial even if it took five seconds. Record the actual bind address and authentication mode as separate deployment observations. The documentation gives a local default and requires authentication on public binds. A successful localhost trial only establishes behavior for that local setup.

Hermes Web Dashboard | Hermes Agent

Measure the session-to-file handoff

Use a synthetic session whose last message names a harmless sample file, then ask an operator to find the file and report its final line. Hermes Workspace documents a combined chat, file, and terminal surface on a standard Hermes installation. Give the official dashboard trial access to any companion editor or terminal you would actually allow on shift, and count time spent switching between those surfaces. Reset both trials to the same starting view and reverse the order on a second pass to reduce familiarity bias. Capture the exact completion evidence and record elapsed seconds only when the file and line match. An interface that saves thirty seconds on a frequent handoff may justify a second surface, provided operators can still complete every required administration task within its deadline.

GitHub - outsourc-e/hermes-workspace: Native web workspace for Hermes Agent — chat, terminal, memory, skills, inspector. · GitHub

Open the official dashboard locally

On a machine with Hermes Agent installed, run hermes dashboard and open http://127.0.0.1:9119 in a browser on that machine. Start with a read-only check. Open the session view and look for a session you recognize. Then check whether the settings page corresponds to the installation you intended to operate before making a configuration change.

If the page never loads, keep the startup output visible and check whether port 9119 is already in use. The documented --port option lets you choose a different port, for example by running hermes dashboard --port 9120 and opening http://127.0.0.1:9120. A page that loads with unexpected settings or sessions calls for checking which Hermes installation you launched before writing anything.

Hermes Web Dashboard | Hermes Agent

Trial Hermes Workspace on a real task

Hermes Workspace is a separate project whose README says it runs on a standard Nous Research Hermes Agent installation. Its documented interface brings chat, files, memory, skills, and a terminal together. Trial it when the operator routinely needs those surfaces during a single task and you can maintain the additional interface.

For an illustrative comparison, give each candidate the same test installation with a session named Inventory Review and a harmless file called inventory-preview.csv. Ask the operator to find the session, identify the configuration it used, and open the file for inspection. Record which steps can be performed in each browser interface and when the operator must switch to a separate terminal or file tool. Choose based on the steps the operator actually repeats.

GitHub - outsourc-e/hermes-workspace: Native web workspace for Hermes Agent — chat, terminal, memory, skills, inspector. · GitHub

Check the bind before changing authentication

For an existing VPS installation, keep the official dashboard bound to 127.0.0.1 and use an authenticated SSH tunnel for browser access. If you need a public bind, the official docs require an authentication provider using a password or OAuth. The old --insecure flag is a deprecated no-op, so changing it will leave the authentication requirement in place.

When remote access fails, first confirm the page responds through the server's loopback address. Then verify the tunnel points to the same host and port. If you intentionally configured a public bind, test it with a clean browser session and verify that authentication is required before any settings or session data appear. Test the agent's messaging channel independently because dashboard access and message delivery can fail for different reasons.

Hermes Web Dashboard | Hermes Agent

Sources