Which Hermes Interface Reaches the Right Profile?
Use Hermes Workspace to exercise the gateway and the Nous dashboard to manage the installation. Verify profile, session, and directory together, then check Docker profiles for shared data volumes.
Use a profile canary across both interfaces
Set up two disposable profiles with a different harmless canary phrase in each. In the Nous dashboard, open the intended profile and record the session identifier shown there. In the outsourc-e Hermes Workspace, send a turn that asks for the canary and the working directory using the same test session. Record the profile and session from observable output, plus the directory the agent actually sees. A working browser page can still open the wrong profile, and a successful turn can execute in the wrong checkout. If the dashboard loads but Workspace reports a refused connection, collect the gateway startup status before changing models. If Workspace reaches the gateway but reports missing APIs, check the installed Hermes Agent version against the Workspace requirements. Keep each observation separate so a gateway failure cannot mask a repository mismatch.
GitHub - outsourc-e/hermes-workspace: Native web workspace for Hermes Agent — chat, terminal, memory, skills, inspector. · GitHubVerify each container owns its data path
Inventory the effective host source mapped to `/opt/data` for every running Hermes Agent container, including containers you opened away from the dashboard. For a directory bind, resolve symlinks and relative paths on the Docker host before assigning an alias in your audit. For a named volume, use the resolved volume identity from the same Docker engine. Compare those identities before running a replacement alongside an existing container. In an illustrative staging test, `personal-a` and `personal-b` may display different profile names yet resolve to the same mount source. That finding outweighs successful browser probes because both containers can write the same session and memory stores. A successful single-owner restart should preserve a disposable session canary and still report the expected execution directory. Capture both results since a stable data volume alone cannot verify the agent’s checkout.
Hermes Docker Setup | Hermes AgentStart with the interface that serves the task
Use the official Hermes web dashboard when you need to inspect sessions, manage API keys or change installation settings. Run hermes dashboard and confirm the local page opens at 127.0.0.1:9119. If you need access from another device, verify the dashboard's authentication configuration and connect over an approved path. Check that the intended session appears before changing anything.
Hermes Workspace from outsourc-e is a separate candidate when you want a browser interface paired to the agent gateway. Evaluate it by sending a harmless prompt and checking that the reply appears under the intended session. If you mainly want a local desktop application, evaluate Nous's Hermes Desktop against the same task. A successful install is less informative than being able to find and resume the session you actually use.
Hermes Web Dashboard | Hermes AgentCheck the directory before changing interfaces
The working directory determines where a fresh task starts looking for relative paths and project files. The dashboard's workspace selector lets you choose a project or enter another path. Select the intended checkout before starting a fresh chat, then ask the agent to report its current directory and read a harmless marker file at the repository root.
In an illustrative example, you have two checkouts named demo-app under different parent directories. Put a file called workspace-check.txt containing the word staging in the staging checkout only. Choose that path and start a fresh chat. The test passes if the reported directory matches the staging checkout and the agent reads the expected word. If you get the other path, correct the selection and repeat with a fresh chat before authorizing any edit.
Hermes Web Dashboard | Hermes AgentTrace an offline indicator to the right service
If Hermes Workspace loads but shows Offline, test the Workspace backend before restarting the agent. On the machine serving the documented local setup, run curl http://localhost:3000/api/sessions. A sessions response, including an empty array, means the backend pairing responds. Refresh the page and send one test prompt before starting another gateway.
If every API call is unauthorized, check whether HERMES_API_TOKEN in Workspace matches API_SERVER_KEY on the gateway. Keep the values out of transcripts. If basic chat works but the interface reports portable mode or missing extended APIs, start the official dashboard with hermes dashboard and refresh. Verify recovery using the particular operation that failed. An updated status indicator alone gives you little evidence that chat or session controls work.
GitHub - outsourc-e/hermes-workspace: Native web workspace for Hermes Agent — chat, terminal, memory, skills, inspector. · GitHub