chat.hjc925.cloud is the browser interface to the Hermes agent. The agent lives on the Anchor Node. It remembers what it learns between sessions. The software is Hermes WebUI, a third-party project. It is not ours. It gives full parity with the terminal: everything that the CLI can do, the browser can do.

​
The two Hermes addresses

These two are often confused. The stock dashboard is not the chat backend. The dashboard is admin tooling and was the reason a separate chat interface was needed.

​
Who holds the login

The chat door has one shared login, not one login for each person. The current holder is recorded on the box.
Change the holder with the Access Manager. Tick the Chat control on that person’s row. The control is a radio button, not a checkbox, because the door has one holder at a time.

​
Layout

The interface has three panels.

Left

Sessions and navigation.

Centre

The conversation.

Right

The workspace files.
The model, the profile and the workspace controls sit in the composer footer, so they stay visible while you write. A ring shows how much of the context window is used.

​
Service facts

All Hermes units are systemd user units under user@1000.service. systemctl is-active hermes-webui answers inactive and systemctl status reports that the unit does not exist, while the door serves normally. Use this instead:
This exact trap produced a false “the service is down” reading on 20 August 2026.

​
Other channels

The agent also answers on Telegram, through the bot @herman_as_a_bot.
Telegram pairing is still not approved. ~/.hermes/channel_directory.json reads "telegram": [], which means no paired sender, while the gateway reports the channel itself as connected. WhatsApp was never set up.