Hermes – Community Web UI with Agent

SeriousM1 pts0 comments

Hermes — Community Web UI

⚡" />

Product

Why Hermes<br>Features<br>Web UI<br>Who it's for<br>烙 Models<br>﫡 Memory

Install

Install<br>Hosting

Learn

樂 ELI5<br>Resources<br>Compare

 Community<br>Get started →

⚡ Open source &middot; Self-hosted &middot; MIT licensed

Hermes<br>Agent

The self-improving AI agent that runs on your server. Layered memory that accumulates across sessions, a cron scheduler that fires while you're offline, and a skills system that saves reusable procedures automatically.

Get Started →

View on GitHub

126k+ GitHub stars<br>Multi-surface access<br>47 built-in tools<br>MIT licensed

Built by Nous Research

Community Web UI — not affiliated with or endorsed by Nous Research. Official site: hermes-agent.nousresearch.com

The core idea

Most tools are excellent in the moment and weak over time

Memory is no longer a differentiator on its own. ChatGPT, Claude, Cursor, and GitHub Copilot all have some form of memory now. With GPT-5.5 and Claude Mythos pushing the frontier in April 2026, Anthropic, OpenAI, and Microsoft are all shipping scheduling and agent features. The category boundaries that existed twelve months ago are blurring fast.

The distinction that matters is not "has memory" vs. "has no memory." It's whether context persists across sessions automatically , whether execution happens on hardware you control , whether you can reach the same agent identity from any device , and whether the system gets meaningfully better at your workflow over time without manual configuration.

Hermes answers yes to all four. It runs as a persistent process on your server. Memory is markdown files in ~/.hermes/. The same agent that answered your Telegram message at 9am is available in your terminal at 2pm, with full context.

Why synthesis matters: The market is converging. Chat assistants added scheduling. Editors shipped cloud agents. CLIs are getting skills. Any single feature is available somewhere else. The value is having all of them in one self-hosted system, running continuously, with a persistent identity that accumulates real knowledge of your stack over time.

Session-scoped tool

You → [Tool] → Answer → Done

(some tools carry memory, but execution is stateless)

Persistent agent

You ↔ [Hermes] ↔ (memory, skills,

schedule, tools,

surfaces)

Memory: ~/.hermes/ (markdown files, editable)

Skills: auto-written from experience

Schedule: cron, runs while you sleep

Surfaces: Telegram &middot; Discord &middot; Slack &middot; browser

Model: your choice, swap anytime

Three pillars

What makes it different

Memory that compounds

Layered memory system: user profile, agent memory, skills, and session history. All stored locally as readable, editable markdown files at ~/.hermes/.

Survives every reboot and model swap

8 optional external memory providers

You never configure it manually

Portable, inspectable, deletable

Memory docs →

Autonomous scheduling

Built-in cron scheduler runs on your server with full access to your memory and skills, and delivers results wherever you want them.

Morning news briefings to Telegram

PR review automation

Test suite monitoring

Blog watchers and price alerts

Scheduling docs →

Reach it from anywhere

Multi-surface access: same agent, same memory. Switch surfaces mid-conversation without losing context.

Telegram &middot; Discord &middot; Slack &middot; WhatsApp

Signal &middot; Matrix &middot; Mattermost &middot; Email &middot; SMS

DingTalk &middot; Feishu &middot; WeCom &middot; BlueBubbles

Home Assistant &middot; browser

Messaging docs →

Full feature set

Everything in one system

47 built-in tools

Web search and extraction, browser automation, code execution, vision analysis, image generation, TTS, subagent delegation, and more.

Tools reference →

Self-improving skills

The agent writes its own skills from experience. Compatible with agentskills.io open standard and shareable via Skills Hub.

Skills docs →

MCP integration

Connect to any MCP server. Hermes can also expose itself as an MCP server for Claude Code, Cursor, or Codex.

MCP docs →

Voice mode

Real-time voice in CLI (Ctrl+B to record), Telegram voice bubbles, Discord voice channels. Supports faster-whisper locally or Groq/OpenAI Whisper.

Voice docs →

6 terminal backends

Local, Docker, SSH, Daytona, Singularity, Modal. Run execution anywhere from a $5 VPS to serverless cloud, sandboxed as needed.

Backend docs →

Personality & SOUL.md

Define the agent's default voice with a global SOUL.md file. 14 built-in personas plus custom personalities via config.

Personality docs →

Agent orchestration

Spawn Claude Code or Codex as sub-agents for heavy coding tasks. Results fold back into Hermes memory. Hermes also runs as an MCP server for other tools.

Orchestration docs →

Security model

7-layer defense in depth: user allowlists, dangerous command approval, Docker isolation, MCP credential filtering, prompt injection scanning, cross-session isolation, input sanitization.

Security docs →

Hermes Web UI

A...

memory middot hermes agent skills docs

Related Articles