Introducing hermes-webui-all-in-one: the full and unified hermes-agent + hermes-webui stack in one single container

[lgc2333]

If you self-host Hermes Agent and want the WebUI on top of it, you've probably run into the same mess I did.

The WebUI's built-in deployment options each have their own problem:

• Single webui container: you get port 8787 and nothing else. The dashboard on 9119, the port Hermes Desktop uses for remote connections, doesn't exist in that image at all.
• Agent + webui as separate containers: now you have two hermes installs and two venvs that drift apart. webui reinstalls every dependency the agent already has, stdio MCP servers can fail to start in its thinner environment, and anything you/agents configure on one side has to be redone on the other.
• Webui's "gateway" bridge mode: sounds like the easy way out, but some features are just broken in that mode, like the thinking content just repeating the model's output. I didn't want to build on that.

So I made hermes-webui-all-in-one. The agent and webui are merged into one uv workspace and shipped as a single image, derived from the official nousresearch/hermes-agent image. No fork, no upstream changes.

What you get:

• One shared venv. Agent and webui both use /opt/.venv, so dependencies are installed exactly once.
• All three ports in one compose: webui 8787, dashboard 9119, gateway API 8642. Hermes Desktop points straight at 9119.
• s6 runs the services, HEALTHCHECK probes webui and gateway, images are cosign-signed, CI builds and pushes on v* tags.
• When upstream releases, you rebuild. That's the whole maintenance story.

If all you want is the WebUI and nothing else, this image is probably more than you need. It's for people who want the whole stack in one place: agent, webui, desktop remote, one shared environment. For browser-only usage the standalone webui image is the better fit.

Try it -> https://github.com/lgc2333/hermes-webui-all-in-one