Hermes WebUI — a community web interface for Hermes Agent

[nesquena]

About six weeks ago I started building a browser interface for Hermes Agent
because I kept wanting to reach it from a phone or a second machine without
opening a terminal. That project is now at v0.50.8, has 791 tests, and 1,500+
people have starred it, so it felt like the right time to open up Discussions
and say hello properly.

What it is

Hermes WebUI is a self-hosted web front-end for Hermes Agent. If you're
running Hermes from the CLI, this gives you the same agent, same memory,
same skills, and same tools from any browser.

Core features:

• Full streaming chat with tool cards, thinking block display, and Mermaid diagrams
• Session manager with search, tags, and project grouping
• Cron scheduler UI — create and manage scheduled jobs without the terminal
• Skills browser — view and manage skills your agent has written
• Memory panel — read and edit memory files directly in the UI
• Workspace file browser with git detection
• 6 built-in themes (dark, light, slate, solarized, monokai, nord)
• Voice input via Web Speech API
• Multi-profile support — separate config and memory per project
• Mobile-responsive layout
• Works with any OpenAI-compatible provider — OpenAI, Anthropic, Groq,
  OpenRouter, Ollama, llama.cpp, and others
• MIT licensed, no telemetry, fully self-hosted

What it isn't

This is a community project. It is not affiliated with or endorsed by
Nous Research. The official Hermes Agent is maintained at
hermes-agent.nousresearch.com — this is an independent UI layer built on
top of it.

Getting started

The quickest path is the install script:

curl -fsSL https://get-hermes.ai/install.sh | bash

Or clone and run manually — the README has full instructions.
If you don't want to self-host, agent37.com offers a managed deployment.

Contributing

8 contributors have already shipped code. The test suite is at 791 tests
and every PR requires them to pass. If you want to pick something up,
open issues labeled enhancement are fair game — comment on the issue
first so work doesn't get duplicated.

Issues labeled hold are blocked on upstream changes. Leave those alone
for now.

This channel

I'll use Announcements for releases and anything that affects existing
installations, such as breaking changes, deprecations, and migration notes. For
questions, bug reports, and feature requests, Issues is still the right
place.

Thanks to everyone who's already contributed, filed issues, and sent
feedback. The project moved faster because of it.

— nesquena

Repo: https://github.com/nesquena/hermes-webui
Site: https://get-hermes.ai

[lowlandsheperd]

Hi, and thank you and the team for building and maintaining Hermes WebUI.

I recently noticed that get-hermes.ai is being featured more prominently on the repository homepage, and the website appears to be becoming a broader public-facing home for the project.

Would you be willing to share any high-level plans for the future of Hermes WebUI and get-hermes.ai?

For example:

Are there any major features or development priorities planned for the coming months?
Is get-hermes.ai mainly intended for documentation and onboarding, or are there plans to expand it further?
Are there any plans based-on/beyond the WebUI itself, such as a native mobile app, native desktop app, or lightweight standalone client? I saw many other related projects in your github.
Are there any longer-term ideas around hosted services, professional support, sponsorship, or other ways to support the project’s continued development?

I completely understand that the roadmap may still be evolving, I am simply curious about the maintainers’ current vision for the project.

Thank you again for your work on Hermes WebUI.

[nesquena]

Hey!

Would you be willing to share any high-level plans for the future of Hermes WebUI and get-hermes.ai?

Sure! The website is meant to be a place to explain Hermes, documentation (for example the Bridge API for all Hermes clients: https://get-hermes.ai/api-docs/), and also setup of all of the available clients for desktop and mobile (https://get-hermes.ai/setup/)

For example:

Are there any major features or development priorities planned for the coming months?

We recently launched the cross platform desktop apps in Rust, the native Android app https://github.com/computerbyte/hermex-android as well as the WebUI extensions library (https://github.com/hermes-webui/hermes-webui-extensions)

And the framework for managing OSS projects like WebUI using agents (https://nesquena.github.io/steward-os/)

Are there any plans based-on/beyond the WebUI itself, such as a native mobile app, native desktop app, or lightweight standalone client?

Absolutely there are. We already have initial clients for almost every platform already and an open Bridge API for clients that anyone can use to build more of them!

Are there any longer-term ideas around hosted services, professional support, sponsorship, or other ways to support the project’s continued development?

Absolutely, nothing is really off the table. We've had requests for enterprise or team based multi-tenant WebUI setups as well as even interest in cloud-based versions. Would absolutely at the minimum love to figure out how to make it break even cost to continue development of the ecosystem. If you have ideas let me know!

[lowlandsheperd]

Thanks for the detailed reply — it’s great to hear there’s a broader plan for the project.

we are currently exploring using Hermes WebUI as a unified way to deploy and manage AI agents for our team, so I mainly wanted to understand the project’s future development plans and goals, and avoid building too many things ourselves if they’re already on the roadmap.

We’re still testing things out, if it works well for our use case, will be very happy to find a way to share/support the project in the future.

[nesquena]

Thanks for the detailed reply — it’s great to hear there’s a broader plan for the project.

we are currently exploring using Hermes WebUI as a unified way to deploy and manage AI agents for our team, so I mainly wanted to understand the project’s future development plans and goals, and avoid building too many things ourselves if they’re already on the roadmap.

We’re still testing things out, if it works well for our use case, will be very happy to find a way to share/support the project in the future.

Sounds great, hope you find it helpful!