Problem Statement
Hermes now offers a stable Web dashboard to configure the agent and chat with it.
The documentation can be found here:
https://hermes-agent.nousresearch.com/docs/user-guide/features/web-dashboard
Just like with OpenClaw, it makes it easier to configure certain elements and to chat with the agent.
Proposed Design
It should be straightforward to implement, with the caveat that most existing functions in the hermes start script which are related to the dashboard would have to be modified and duplicated.
The existing functions would now control the real Web dashboard and the new ones would be to control the existing API endpoint. I believe OpenClaw also offers an API endpoint, so these functions could be ported there as well.
agents/hermes/Dockerfile.base
- Add
pty to the list of packages to install (HERMES_UV_EXTRAS="messaging web pty").
agents/hermes/Dockerfile
- Use
npm to build the needed components found in /opt/hermes/ui-tui and /opt/hermes/web.
- Maybe this is also here that we have to introduce the new port for the OpenShell forward?
agents/hermes/start.sh
- Use socat to bridge 9119 from OpenShell to 19119 where the Web dashboard would be launched.
- Introduce an alias? So that
hermes dashboard launches the server on the correct port and in the background (something like hermes dashboard --port 19119--tui &).
- Launch the dashboard?
Alternatives Considered
No response
Category
enhancement: feature
Checklist
Problem Statement
Hermes now offers a stable Web dashboard to configure the agent and chat with it.
The documentation can be found here:
https://hermes-agent.nousresearch.com/docs/user-guide/features/web-dashboard
Just like with OpenClaw, it makes it easier to configure certain elements and to chat with the agent.
Proposed Design
It should be straightforward to implement, with the caveat that most existing functions in the hermes start script which are related to the dashboard would have to be modified and duplicated.
The existing functions would now control the real Web dashboard and the new ones would be to control the existing API endpoint. I believe OpenClaw also offers an API endpoint, so these functions could be ported there as well.
agents/hermes/Dockerfile.base
ptyto the list of packages to install (HERMES_UV_EXTRAS="messaging web pty").agents/hermes/Dockerfile
npmto build the needed components found in/opt/hermes/ui-tuiand/opt/hermes/web.agents/hermes/start.sh
hermes dashboardlaunches the server on the correct port and in the background (something likehermes dashboard --port 19119--tui &).Alternatives Considered
No response
Category
enhancement: feature
Checklist