me: can u build https://github.com/brightmann/urd on brightmann.github.io/urd?
Build is done and verified locally. One thing to flag: Urodele only supports domain-root deploys, so I patched it for the /urd subpath — all nav, post, tag, pagination, edit and image links now carry the /urd prefix, the editor config points at brightmann/urd, and the deploy workflow uses the official Pages actions. The demo post renders with its images and the build is green.
To push it I need a fresh PAT for brightmann/urd (Contents + Workflows, since the push includes the workflow file — the one from yesterday is revoked). Also enable Actions on the fork, or the workflow won't run.
me: the github pat here...
Pushed. The first workflow run failed at "Setup Node.js" — pnpm 9 breaks on this repo (pnpm store path errors out), so I pinned pnpm 12 and pushed the fix; a new run is in progress now.
One step needs you: GitHub Pages isn't enabled on the repo yet, and my token can't enable it. Go to Settings → Pages → Build and deployment → Source, and pick GitHub Actions. If you do it now, this run may deploy straight away; if not, re-run it from the Actions tab after.
Update: the build is green now with pnpm 12 — only the deploy failed, because Pages still isn't enabled. Once you set Settings → Pages → Source to GitHub Actions, re-run the workflow from the Actions tab and it should go live.
me: can u create a test post?
Test post is pushed. The site's already live too — you enabled Pages and the re-run deployed successfully. I'm waiting on this push's deploy check now and will confirm the post page once it's up.
It's live: Test Post — 200, body text and code block both render, and it shows on the homepage too. The push-to-live loop works end to end now.
The post is just a placeholder — delete posts/Test-Post.json whenever you want it gone, or edit it in the built-in editor once you log in with a GitHub token.
我: i cannot paste an article with many paragraphs directly?
Right — not into the .json file directly. That file is structured data: one node per paragraph, and every quote has to be escaped. Pasting a whole article in there just breaks the JSON, like the iframe did.
Use the built-in editor instead, it's made for this:
Open https://brightmann.github.io/urd/login and paste a GitHub token — the same one you used for pushes works (it stays in your browser, only the site uses it).
Go to /edit, paste the article. The editor splits it into paragraphs automatically, and keeps bold/headings if you paste from a web page or doc.
Save — it writes the .json to the repo, and the site rebuilds in about 2 minutes.
Or, if you'd rather not log in: paste the article here and I'll turn it into a post file and push it for you.
我:
我:pls fix it。which json file the pic means?
None — no JSON file at all. The error wasn't about a post.
The /login/ page is only the GitHub OAuth callback page. It tries to exchange a login code with a server URL that's empty in your config (you use direct token login, no OAuth), so it ended up fetching the login page itself — HTML — and choked trying to parse that as JSON. That's the "line 1 column 1": the first character of the HTML.
I fixed it: the page now skips that exchange when OAuth isn't set up and just sends you home. It's pushed and deployed. I'm checking the live login page in a browser now to confirm the popup is gone.
One correction to my earlier message: the token box isn't on /login/ at all — it's the small triangle button in the site header on the homepage. Click that, paste your token, and you're in.
Confirmed live: opening /login/ now goes straight to the homepage, no popup. The homepage shows all four posts, and the login button is in the header as expected.
By the way, your 战马 post is live too — it came through cleanly with the video.
我: how to generate the github token? choose which permissions for the token?
Name it something like urd-editor, pick an expiration.
Repository access → Only select repositories → pick brightmann/urd.
Under Repository permissions, set Contents to Read and write. That's the only permission it needs — the editor just reads and writes the post files. Leave everything else at No access.
Generate it, copy the value (it only shows once), and paste it into the login box on the site.
Don't use a classic token with full repo scope — the fine-grained one limited to this repo is safer, and it's what the login page itself links to.
me:
me: it's just loading, show nothing. something wrong?
Yes — the editor page is stuck on its loading spinner and never finishes. The page itself and its data load fine from my checks, so something in the editor's startup is failing silently (it has no error message — if any step fails, it just spins forever).
I'm reproducing it in a browser right now to read the exact error from the console. Once I see what's failing I'll fix it.
Good news on the diagnosis: I reproduced the stuck editor in a browser too, so it's not just your setup — the page really never finishes loading.
The data it needs all loads fine, so something in the editor's startup is failing silently. I've pushed a fix for that part: instead of spinning forever, the page will now show the actual error message. I'm checking what it says right now, and then I'll fix the real cause.
That check told me something useful: no error box appeared, so the editor isn't crashing — it's hanging on one step without ever finishing. I've added step markers to the page so it now shows exactly where it stops ("loading post list…", "loading autosave…", and so on). That's deployed, and I'm checking what it says right now.
The markers didn't show up at all — not even the first one. That points to the browser showing a cached copy of the page rather than the new code (GitHub Pages caches pages for a few minutes). I'm re-checking with a hard refresh now.
Found it — and it was my bug. The editor loads the post list from /urd/api/post/list, but my subpath code built the URL as /urdapi/post/list (missing slash), which 404s. The editor got an HTML error page instead of JSON and died silently on the spinner.
Fixed it to build the URL properly, pushed and deployed. I'm verifying the editor loads now.
The fix is deployed, but the live site is still serving the previous build — I checked, and the page the browser loaded is the pre-fix version (GitHub Pages takes a few minutes to roll out a new deploy). That's why the same error showed up again. I'm waiting for the new build to go live and will re-check the editor then.
Correction to my last message: I dug deeper and the fix actually is live — the live code contains the corrected URL. The browser check ran against a stale copy from before the new build rolled out. Re-checking the editor now.
The live code is verified correct now — I compared it byte for byte with the fixed build, and the fetch URL is right. So the error my browser checks keep showing is that browser holding onto the old cached copy, not the live site. I'm re-testing with a fresh URL that bypasses the cache to confirm.
The fix is in and the debug text is cleaned up. The final check on the clean editor is running now — I'll confirm once it's done.
Fixed and verified live. The editor now opens properly — title field, tag input, editing area, and Publish / Save as draft all there, no error, no debug text left.
The cause was my own subpath patch: the editor asked for the post list at /urdapi/... instead of /urd/api/... (a missing slash), got an error page back instead of data, and died silently on the spinner.
One thing: if your Firefox still shows the spinner, hard-refresh the page (Ctrl+F5) — browsers hold onto the old cached copy for a while, and that bit me during testing too.
me: pls fix it-
This is a new error, and that's actually progress: the last fix worked, the editor now gets past loading the post list and fails one step later, at autosave.
The editor autosaves drafts to the browser's IndexedDB storage. Firefox throws that "quota" error when it can't create that database — which happens when the disk is nearly full. Your C: drive had only 2.77 GB free when we checked on Nov 13, so that's the likely cause. Freeing disk space should bring autosave back.
I've fixed the code so the editor no longer dies over this: it will load even when storage is broken, autosave just quietly won't work, and Publish / Save as draft still work fine since those go to GitHub, not local storage. The fix is committed locally and the build passes.
I need a fresh token to push it — same as last time, a fine-grained PAT for brightmann/urd with Contents + Workflows. You can revoke it after the deploy succeeds.
me: my github pat here...
Pushed and deployed. Verifying the editor loads live now — I'll confirm in a moment.
Fixed and verified live — the editor loads now, no error.
Try it in your Firefox. If it still shows the old error, hard-refresh (Ctrl+F5) — your browser may be holding the cached copy. And freeing up disk space should bring autosave back; without it, the editor still works, it just won't autosave locally.
You can revoke the token now — the deploy succeeded.
Because the iframe code was pasted in as plain text. The editor stores pasted HTML as a text paragraph and escapes it when rendering, so the page showed the code itself instead of a video. The editor has no raw-HTML block — videos only work as a proper video block.
I fixed the 恋之火 post by converting that paragraph into a video block, and verified live: the page now has a real YouTube embed for 白光《戀之火》.
For next time: in the editor, paste the YouTube link itself, not the <iframe> embed code.
Right — the post body doesn't support HTML code. It stores structured blocks (paragraphs, headings, images, video), not HTML. Anything pasted as HTML becomes plain text and shows up as code on the page. That's what happened with both the iframe in 恋之火 and the whole ifeng article in 扬州.
扬州 is fixed and verified live: the article now renders as 148 proper paragraphs with all 63 photos showing, and none of the text was lost.
For pasting articles: paste the text itself (or paste into the editor and let it split into paragraphs), never the page's HTML source.
me: u mean the editor support "what u see is what u get" ?
Yes, exactly — it's WYSIWYG. What you type and format in the editor is what the published post looks like: headings, bold, images, video, all render the same.
The catch is only about what you paste: paste the article as you see it on the page (the rendered text and pictures), and the editor keeps the formatting. Paste the page's HTML source code, and it treats that code as plain text — which is what happened with 扬州.
Hermes WebUI: The best way to use Hermes Agent from the web or from your phone!
https://get-hermes.ai/setup
Hermes Web UI
Hermes Agent is a sophisticated autonomous agent that lives on your server, accessed via a terminal or messaging apps, that remembers what it learns and gets more capable the longer it runs.
Hermes WebUI is a lightweight, dark-themed web app interface in your browser for Hermes Agent.
Full parity with the CLI experience - everything you can do from a terminal, you can do from this UI. No build step, no framework, no bundler. Just Python and vanilla JS.
Layout: three-panel. Left sidebar for sessions and navigation, center for chat,
right for workspace file browsing. Model, profile, and workspace controls live in
the composer footer — always visible while composing. A circular context ring
shows token usage at a glance. All settings and session tools are in the
Hermes Control Center (launcher at the sidebar bottom).
Setup Hermes so you can access it natively on every device:
Light mode with full profile support
Customize your settings, configure a password
Workspace file browser with inline preview
Session projects, tags, and tool call cards
This gives you nearly 1:1 parity with Hermes CLI from a convenient web UI which you can access securely through an SSH tunnel from your Hermes setup. Single command to start this up, and a single command to SSH tunnel for access on your computer. Every single part of the web UI uses your existing Hermes agent and existing models, without requiring any additional setup.
Most AI tools reset every session. They don't know who you are, what you worked on, or what
conventions your project follows. You re-explain yourself every time.
Hermes retains context across sessions, runs scheduled jobs while you're offline, and gets
smarter about your environment the longer it runs. It uses your existing Hermes agent setup,
your existing models, and requires no additional configuration to start.
What makes it different from other agentic tools:
Persistent memory — user profile, agent notes, and a skills system that saves reusable
procedures; Hermes learns your environment and does not have to relearn it
Self-hosted scheduling — cron jobs that fire while you're offline and deliver results to
Telegram, Discord, Slack, Signal, email, and more
10+ messaging platforms — the same agent available in the terminal is reachable from your phone
Self-improving skills — Hermes writes and saves its own skills automatically from experience;
no marketplace to browse, no plugins to install
Provider-agnostic — OpenAI, Anthropic, Google, DeepSeek, OpenRouter, and more
Orchestrates other agents — can spawn Claude Code or Codex for heavy coding tasks and bring
the results back into its own memory
Self-hosted — your conversations, your memory, your hardware
vs. the field(landscape is actively shifting — see docs/why-hermes.md for the full breakdown):
OpenClaw
Claude Code
Codex CLI
OpenCode
Hermes
Persistent memory (auto)
Yes
Partial†
Partial
Partial
Yes
Scheduled jobs (self-hosted)
Yes
No‡
No
No
Yes
Messaging app access
Yes (15+ platforms)
Partial (Telegram/Discord preview)
No
No
Yes (10+)
Web UI (self-hosted)
Dashboard only
No
No
Yes
Yes
Self-improving skills
Partial
No
No
No
Yes
Python / ML ecosystem
No (Node.js)
No
No
No
Yes
Provider-agnostic
Yes
No (Claude only)
Yes
Yes
Yes
Open source
Yes (MIT)
No
Yes
Yes
Yes
† Claude Code has CLAUDE.md / MEMORY.md project context and rolling auto-memory, but not full automatic cross-session recall
‡ Claude Code has cloud-managed scheduling (Anthropic infrastructure) and session-scoped /loop; no self-hosted cron
The closest competitor is OpenClaw — both are always-on, self-hosted, open-source agents
with memory, cron, and messaging. The key differences: Hermes writes and saves its own skills
automatically as a core behavior (OpenClaw's skill system centers on a community marketplace);
Hermes is more stable across updates (OpenClaw has documented release regressions and ClawHub
has had security incidents involving malicious skills); and Hermes runs natively in the Python
ecosystem. See docs/why-hermes.md for the full side-by-side.
Quick start
Run the repo bootstrap:
git clone https://github.com/nesquena/hermes-webui.git hermes-webui
cd hermes-webui
python3 bootstrap.py
Or keep using the shell launcher:
./start.sh
For self-hosted VM or homelab installs, ctl.sh wraps the common daemon lifecycle commands without requiring fuser or pkill:
ctl.sh start runs the bootstrap in foreground/no-browser mode behind the daemon wrapper, writes logs to ~/.hermes/webui.log, and respects .env plus inline overrides such as HERMES_WEBUI_HOST=0.0.0.0 ./ctl.sh start.
Stopping the server. Each launch method has its own stop path because only ctl.sh start writes a PID file (~/.hermes/webui.pid):
Launch method
How to stop
python3 bootstrap.py
Ctrl-C in the terminal (runs in the foreground)
./ctl.sh start
./ctl.sh stop (sends SIGTERM, waits, then SIGKILL)
Detached bootstrap.py (no --foreground) or ./start.sh
Find the PID via lsof -i :8787 (or ss -tlnp) and kill it
./ctl.sh stop cannot stop a server launched by bootstrap.py or start.sh directly — it only manages processes it started itself.
How chat runs by default. WebUI runs the Hermes agent in-process, reading
your HERMES_HOME config directly. It does not connect to an external
Hermes/agent OpenAI-compatible API server to run chat. HERMES_API_URL is only
read by the Tasks/cron health probe and does not route chat.
Two options if you run an external endpoint:
Use its models as a chat provider (supported today): add it in
Settings → Providers as a custom OpenAI-compatible provider with
base_url = http://127.0.0.1:8642/v1 and your bearer token.
Route chat through a Hermes Gateway API server (supported today via
HERMES_WEBUI_CHAT_BACKEND=gateway): see docs/advanced-chat-setup.md.
Full agent-loop delegation is not yet shipped; tracked in #1925.
Two optional, self-hosted-deployment features — attaching dynamic session-recall prefill to browser turns (Joplin/Obsidian/Notion/llm-wiki routers), and routing browser chat through a running Hermes Gateway — are documented in docs/advanced-chat-setup.md. Most users need neither.
The bootstrap will:
Detect Hermes Agent and, if missing, attempt the official installer (curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash).
Find or create a Python environment with the WebUI dependencies.
Start the web server and wait for /health.
Open the browser unless you pass --no-browser.
Drop you into a first-run onboarding wizard inside the WebUI.
Native Windows is not supported for this bootstrap yet. Use Linux, macOS, or WSL2.
For Windows / WSL auto-start at login, see docs/wsl-autostart.md.
Memory: community-measured ~330 MB native vs ~1080 MB with WSL2+Docker (varies by configuration).
What works: chat, workspace browser, session management, all themes.
Known limitations: some POSIX-style file paths surface in the workspace browser; bash-assuming agent tools may not work natively.
Native Windows setup: install Python 3.11+, then from the hermes-agent root in PowerShell: python -m venv venv → pip install -r requirements.txt → pwsh .\start.ps1 (it auto-discovers venv\Scripts\python.exe).
WSL2 relationship: not a prerequisite — a WSL2-built venv (venv/bin/python, ELF) isn't invokable by native Windows Python, so use the native setup above. WSL2 stays useful as a parallel install if you want the full bootstrap.py + Linux runtime.
If provider setup is still incomplete after install, the onboarding wizard will point you to finish it with hermes model instead of trying to replicate the full CLI setup in-browser.
For a step-by-step walkthrough of the wizard, provider choices, local model server Base URLs, and safe re-runs, see docs/onboarding.md.
If an AI assistant is helping with install, reinstall, bootstrap, provider setup, or first-run support, have it read docs/onboarding-agent-checklist.md before running commands or inspecting logs.
Features
Chat and agent
Streaming responses via SSE (tokens appear as they are generated)
Multi-provider model support -- any Hermes API provider (OpenAI, Anthropic, Google, DeepSeek, Nous Portal, OpenRouter, MiniMax, Xiaomi MiMo, Z.AI); dynamic model dropdown populated from configured keys
Send a message while one is processing -- it queues automatically
Edit any past user message inline and regenerate from that point
Retry the last assistant response with one click
Cancel a running task directly from the composer footer (Stop button next to Send)
Tool call cards inline -- each shows the tool name, args, and result snippet; expand/collapse all toggle for multi-tool turns
Subagent delegation cards -- child agent activity shown with distinct icon and indented border
Detached child results are delivered to the parent as internal wakeups. Their raw prompts and completion toasts do not appear as messages from the user; the parent can summarize the results in its own reply. Ordinary background-process wakeups remain visible. A completed parent reply does not, by itself, cancel or suppress outstanding children; a later result may still start a follow-up turn.
Thinking/reasoning display -- collapsible gold-themed cards for Claude extended thinking and o3 reasoning blocks
Approval card for dangerous shell commands (allow once / session / always / deny)
SSE auto-reconnect on network blips (SSH tunnel resilience)
File attachments persist across page reloads and are stored outside the active workspace by default (~/.hermes/webui/attachments/<session_id>/, or HERMES_WEBUI_ATTACHMENT_DIR/<session_id>/ when configured)
Message timestamps (HH:MM next to each message, full date on hover)
Code block copy button with "Copied!" feedback
Syntax highlighting via Prism.js (Python, JS, bash, JSON, SQL, and more)
Safe HTML rendering in AI responses (bold, italic, code converted to markdown)
Bare HTTP(S) URLs are auto-linked without absorbing adjacent CJK prose; Unicode IDN host separators and raw-CJK IRI paths remain linkable
Local file links: a file:/// URI in a reply renders through the media route (inline preview for images/audio/video, download otherwise). Windows drive-letter URIs (file:///C:/...) resolve to the drive path on a Windows server; on a POSIX server the leading separator is preserved so a /C:/... request stays absolute and can never alias a workspace-relative file. Only local authorities are served — a file://<host>/... UNC reference is rejected (never silently rewired to a local path), and the file must live under an allowed root (HERMES_HOME, /tmp, the active workspace, or MEDIA_ALLOWED_ROOTS)
rAF-throttled token streaming for smoother rendering during long responses
Context usage indicator in composer footer -- token count, cost, and fill bar (model-aware)
Sessions
Create, rename, duplicate, delete, search by title and message content
Session actions via ⋯ dropdown per session — pin, move to project, archive, duplicate, delete
Pin/star sessions to the top of the sidebar (gold indicator)
Pinned-conversation limits apply separately to each session's owning profile; root/default aliases share a limit. Unpin an empty session before switching its profile through chat or /goal.
Archive sessions (hide without deleting, toggle to show)
Session projects -- named groups with colors for organizing sessions; delegated subagent sessions have no project of their own and follow their nearest ancestor's project in the project filter and the Unassigned chip; forks and other child sessions keep their own project, so a fork moved to "No project" stays Unassigned
Delegated subagent sessions nest under their parent row. When that parent is filtered out of the current view (project, source tab, hidden), the subagent is hidden with it rather than shown as a stray top-level "Subagent Session"; a subagent without the cross-surface flag (for example in the all-profiles view) stays a top-level row when its parent is in the other (CLI/TUI) tab, was never imported, or is itself shown as a top-level subagent row, and a subagent that matches an active sidebar search is always listed
Project bindings -- right-click a project chip and pick Project settings… to pin a default workspace (or several workspaces, with one marked default) and a model. The chip's + (and New Chat while the project filter is active) then opens a session already in that workspace/model. The reasoning-effort binding stays in the API (POST /api/projects/bind) but is dormant: the dialog no longer offers the row, and nothing applies a stored value to a new session any more — the only mechanism would be the profile-wide reasoning-effort preference (the same agent.reasoning_effort setting the /reasoning command writes), so a row inside a per-project dialog read as per-project while silently moving the whole profile's effort; it comes back with per-session effort (#7881)
Session tags -- add #tag to titles for colored chips and click-to-filter
Clicking a session tag chip filters the list without opening the conversation.
Grouped by Today / Yesterday / Earlier in the sidebar (collapsible date groups)
Download as Markdown transcript, full JSON export, or import from JSON
Create a public read-only share link for the active conversation from the Control Center; shared pages show a sanitized transcript snapshot without workspace, profile, or live controls
Sessions persist across page reloads and SSH tunnel reconnects
Model and reasoning-effort selections are restored per session; new-session defaults and legacy-session reasoning fallback use that session's profile configuration, including an authoritative HERMES_CONFIG_PATH for root; named profiles use their own config.yaml unless the override resolves inside that profile home
Browser tab title reflects the active session name
CLI session bridge -- CLI sessions from hermes-agent's SQLite store appear in the sidebar with a gold "cli" badge; click to import with full history and reply normally
Token/cost display -- input tokens, output tokens, estimated cost shown per conversation (toggle in Settings or /usage command)
Workspace file browser
Directory tree with expand/collapse (single-click toggles, double-click navigates)
Breadcrumb navigation with clickable path segments
Preview text, code, Markdown (rendered), and images inline
Chat links using workspace://path/to/file open files in the right-side preview pane
Edit, create, delete, and rename files; create folders
Binary file download (auto-detected from server)
File preview auto-closes on directory navigation (with unsaved-edit guard)
Dismissing the workspace panel is respected: resizing the viewport or showing the
on-screen keyboard no longer force-reopens the panel after you close it (#6710)
Previews report their real load outcome -- a broken source is reported as a
failure instead of a silent success -- and a response that never settles is
released by a bounded wait so the panel still opens; the source keeps loading
and a late failure is surfaced in the status line (#6710)
Git detection -- branch name and dirty file count badge in workspace header
Right panel is drag-resizable
Syntax highlighted code preview (Prism.js)
Voice input
Microphone button in the composer (Web Speech API)
Tap to record, tap again or send to stop
Live interim transcription appears in the textarea
Auto-stops after ~2s of silence
Appends to existing textarea content (doesn't replace)
Hidden when browser doesn't support Web Speech API (Chrome, Edge, Safari)
A saved fallback from browser speech recognition to server-side recording expires after 24 hours. Preferences stored by older versions get a 24-hour window on first use after upgrading. On reload after expiry, the mic returns to normal capture selection: server transcription takes priority when available; otherwise it uses browser speech recognition.
Profiles
Profile chip in the composer footer -- dropdown showing all profiles with gateway status and model info
Gateway status dots (green = running), model info, skill count per profile
Profiles management panel -- create, switch, and delete profiles from the sidebar
Clone config from active profile on create
Optional custom endpoint fields on create -- Base URL and API key written into the profile's config.yaml at creation time, so Ollama, LMStudio, and other local endpoints can be configured without editing files manually
Seamless switching -- no server restart; reloads config, skills, memory, cron, models
Per-session profile tracking (records which profile was active at creation)
Authentication and security
Optional password auth -- off by default, zero friction for localhost
Enable via HERMES_WEBUI_PASSWORD env var or Settings panel
Installed PWAs work best with WebUI's own password. Reverse proxies are supported, but proxy basic auth can block the service-worker update fetches an installed app needs and leave it on a blank screen after an update; see docs/troubleshooting.md for recovery steps.
Optional passkeys/WebAuthn -- register from Settings -> System after signing in with a password; the login page only shows passkey sign-in after at least one passkey exists
After registering at least one passkey, Settings -> System can remove the password and keep passkey-only sign-in enabled. Password auth remains the bootstrap/recovery path until you choose to go passwordless; passkeys are same-origin and stored locally in the WebUI state directory
Optional native OIDC login for WebUI sessions -- configure webui_oidc.issuer, client_id, allow_claim, and allow_values in config.yaml, or set the matching HERMES_WEBUI_OIDC_* environment variables. OIDC stays disabled until all four are present, and startup prints a warning if the config is partial.
Native OIDC sends the client secret in the token-request form body (client_secret_post) by default. When the provider's discovery document only advertises client_secret_basic in token_endpoint_auth_methods_supported (common with strict OIDC stacks such as zitadel/oidc), the secret automatically moves to the HTTP Basic header instead. Set webui_oidc.token_auth_method (or HERMES_WEBUI_OIDC_TOKEN_AUTH_METHOD) to client_secret_basic or client_secret_post to pin a method explicitly.
Native OIDC stores the PKCE/state nonce flow in process memory. That works for the shipped single-process server, and it also works behind a load balancer when callbacks stay sticky to the same WebUI instance. Multi-instance deployments need session affinity, or the callback can land on a different process and fail state validation.
Signed HMAC HTTP-only cookie with 24h TTL
Minimal dark-themed login page at /login
Security headers on all responses (X-Content-Type-Options, X-Frame-Options, Referrer-Policy)
20MB POST body size limit
CDN resources pinned with SRI integrity hashes
Themes
Appearance is split into two axes: Theme (system, dark, light) and Skin
(default, ares, mono, slate, poseidon, sisyphus, charizard,
sienna, catppuccin, nous, geist-contrast / Geist Contrast)
Switch via Settings -> Appearance (instant live preview) or /theme <theme-or-skin>
Persists across reloads (server-side in settings.json + localStorage for flicker-free loading)
Skins use data-skin plus CSS variables; dark mode resolves through the
.dark class, not a data-theme custom-theme axis — see THEMES.md
Settings and configuration
Hermes Control Center (sidebar launcher button) -- Conversation tab (export/import/clear), Preferences tab (model, send key, theme, language, all toggles), System tab (version, password)
Send key: Enter (default) or Ctrl/Cmd+Enter
Send-key on touch devices: plain Enter inserts a newline on phones (iPhone/iPod, Android phones) and on tablets / iPadOS / touch-capable Macs that only expose a coarse pointer (no attached hardware keyboard), matching the software keyboard's return key. Devices that report a fine pointer (for example, a tablet with a hardware keyboard) keep the configured physical-keyboard send-key behavior. The configured shortcut and the Send button remain available for sending.
Show/hide CLI sessions toggle (enabled by default)
Token usage display toggle (off by default, also via /usage command)
Task list in chat toggle (off by default) -- a collapsible task strip pinned at the top of the chat area, summarising the current session's todos. While it is on, the sidebar Todos panel is hidden and the workspace-panel Todos toggle is disabled with an explanation, so the same list is never shown twice; switch it back off in Settings -> Appearance to restore the sidebar panel and re-enable the workspace toggle.
Control Center always opens on the Conversation tab; resets on close
Unsaved changes guard -- discard/save prompt when closing with unpersisted changes
Cron completion alerts -- toast notifications and unread badges scoped to the active profile on the Tasks tab and session sidebar
Background agent error alerts -- banner when a non-active session encounters an error
Approval and clarification browser alerts notify once per pending owner when its session is not actively viewed. Local approval dismissal hides attention without resolving the prompt; resolution, replacement, and cancellation retire that owner's alert state. Denied or failed notification delivery can retry while the prompt remains pending.
Slash commands
Type / in the composer for autocomplete dropdown
Plain skills match case-insensitive keywords in their name or description; built-in, agent/plugin, and bundle commands keep prefix matching and take precedence over a same-slug skill
A canonical model_aliases entry and a provider-qualified legacy target name their own
route. The target is authoritative, so /model sol selects that provider even when a
same-named model exists on another provider. A canonical entry also takes precedence over a
legacy entry with the same name.
An unqualified legacy target names only a model, so it keeps the ordinary lookup: the
active provider first, then the normal fuzzy match. This is the behavior /model had before,
and it is unchanged.
Aliases that carry their own endpoint or credentials are resolved server-side; the browser only
receives the model, the provider id, and an opaque route id, never a base URL or key.
On the in-process backend, an alias with its own base_url follows Hermes's direct-alias
credential rules: its declared api_key/key_env wins; otherwise only a credential resolved
for that endpoint's own host is sent (for example an OpenRouter key to openrouter.ai), never
the provider label's key to an unrelated host. The alias's provider still selects its wire protocol.
Gateway and runner chat support provider-only aliases by sending the resolved target model
and provider, not the alias name: their runtime does not share WebUI's alias registry. Aliases
that explicitly declare base_url, api_key, or key_env need the in-process backend. External
chat starts, wakeups, Gateway regeneration, and Gateway goal kickoffs reject them with HTTP 400 and
reason: model_alias_requires_in_process_backend before dispatch; a new Gateway goal is not
set. Runner regeneration remains unsupported (HTTP 409), regardless of alias selection.
Ambient credentials resolved for a provider-only alias do not count as alias overrides.
The session retains its target model and profile-bound opaque route id, including Gateway
success/error writeback, so a later backend switch can still resolve the original alias.
A session stores that opaque route id, not the endpoint, so an alias that is later deleted or renamed
leaves the session pointing at a route nothing owns. That send fails closed — on every backend, the
in-process worker, the gateway and the runner alike — with a controlled "model alias unavailable"
error instead of quietly falling back to another provider; pick the model again to store a live route.
With HERMES_WEBUI_RUNTIME_ADAPTER=runner-local, /goal <text> returns HTTP 501
(status: unsupported) without changing an existing goal or starting a run. The
runner contract does not yet provide atomic goal replacement and kickoff; WebUI
never substitutes local goal execution. /goal status, pause, resume, and
clear delegate to the runner when supported. Legacy-direct and legacy-journal
goal kickoff behavior is unchanged for supported routes. Normal runner chat supports provider-only model aliases.
/goal <text> reads Hermes Agent's inline completion-contract lines (outcome:,
verification:, constraints:, boundaries:, stop when:) into the goal's contract
and keeps the first plain line(s) as the goal. /goal gate … is refused with HTTP 400
(error: unsupported_gate) on every backend, without changing the goal or starting a run:
gates rerun shell commands after every turn and WebUI has no rule yet for who may add them.
Use /goal -- <text> for a goal that starts with a control word such as gate or pause.
Server-initiated turns retain the pre-session stale-Agent-runtime barrier. It
runs before loading the session; named-profile alias and Gateway routing happen
only after admission. A stale default local runtime can therefore reject a wakeup
before the session's named-profile Gateway ownership is known.
Panels
Chat -- session list, search, pin, archive, projects, new conversation
Tasks -- view, create, edit, run, pause/resume, delete cron jobs; run history; completion alerts; a Scripts subtab for a read-only browse of the profile's ~/.hermes/scripts/ directory (see docs/scripts-panel.md)
Skills -- list all skills by category, search, preview, create/edit/delete; linked files viewer
Memory -- view and edit MEMORY.md and USER.md inline
Todos -- live task list from the current session; hidden while the in-chat task list toggle is on, which also disables the workspace-panel Todos tab
Insights -- token, cost, and skill-usage analytics; period presets (7/30/90/365 days) plus a Custom range with start/end date pickers
Artifacts -- files changed in the session and Skills Used, with a separate skill count and per-skill use counts
Spaces -- add, rename, remove workspaces; quick-switch from topbar
Mobile responsive
Hamburger sidebar -- slide-in overlay on mobile (<640px)
Sidebar top tabs stay available on mobile; no fixed bottom nav stealing chat height
Files slide-over panel from right edge
Touch targets minimum 44px on all interactive elements
Full-height chat/composer on phones without bottom-nav spacing
Desktop layout completely unchanged
Configuration & access
start.sh auto-detects almost everything; the subsections below cover the knobs for when it can't, and how to reach the UI remotely.
What start.sh discovers automatically
Thing
How it finds it
Hermes agent dir
HERMES_WEBUI_AGENT_DIR, then valid authoritative run_agent.py checkouts, the hermes launcher, the selected Python, valid fallback checkouts, and finally marker-only roots
Python executable
HERMES_WEBUI_PYTHON, Agent venv, interpreter that proved the Agent root, .venv in this repo, then system Python
State directory
HERMES_WEBUI_STATE_DIR env, then $HERMES_HOME/webui (Windows default %LOCALAPPDATA%\hermes\webui, POSIX default ~/.hermes/webui)
Default workspace
HERMES_WEBUI_DEFAULT_WORKSPACE env, then ~/workspace, then state dir
Port
HERMES_WEBUI_PORT env or first argument, default 8787
Before it installs the agent or writes any state, the bootstrap binds the resolved host and port as a preflight. If another service already holds the port, it stops right there, names the address it could not bind, and prints a free alternative to pass to ./start.sh <port> or set as HERMES_WEBUI_PORT in .env. The running service and your existing configuration are left untouched. When the listener on that port is a healthy WebUI -- the instance you already started -- bootstrap reports it ready and leaves it alone, browser included; only a foreign service gets the conflict message.
If discovery finds everything, nothing else is required.
Overrides (only needed if auto-detection misses)
export HERMES_WEBUI_AGENT_DIR=/path/to/hermes-agent
export HERMES_WEBUI_PYTHON=/path/to/python
export HERMES_WEBUI_PORT=9000
export HERMES_WEBUI_AUTO_INSTALL=1 # enable auto-install of agent deps (disabled by default)
./start.sh
Auto-install requires the selected Agent to match HERMES_WEBUI_AGENT_DIR or the Agent under HERMES_HOME, and still checks ownership and permissions.
Where sessions and state are stored. Note (upgrade): the default now follows HERMES_HOME — if you previously relocated HERMES_HOME to a non-default base without setting HERMES_WEBUI_STATE_DIR, your WebUI state now resolves to $HERMES_HOME/webui instead of the old platform-default ~/.hermes/webui. To keep using the old location, set HERMES_WEBUI_STATE_DIR to it (or move the directory). Installs with HERMES_HOME unset or at the default base are unaffected.
HERMES_WEBUI_SETTINGS_FILE
<state dir>/settings.json
Optional path for this instance's WebUI settings file (sessions, workspaces and projects stay in the state directory). Read once at startup, so restart after changing it
HERMES_WEBUI_DEFAULT_WORKSPACE
~/workspace
Default workspace
HERMES_WEBUI_DEFAULT_MODEL
(provider default)
Optional model override; leave unset to use the active Hermes provider default
HERMES_WEBUI_PASSWORD
(unset)
Set to enable password authentication
HERMES_WEBUI_CSP_CONNECT_EXTRA
(unset)
Optional space-separated http(s):// or ws(s):// origins to append to the enforced and report-only CSP connect-src directives for trusted reverse-proxy, tunnel, or extension sidecar deployments
HERMES_WEBUI_CSP_IMG_EXTRA
(unset)
Optional space-separated http(s):// image origins (wildcard subdomain and port allowed), or the bare https: / http: scheme, added to the CSP img-src. Remote images are blocked by default so an assistant reply cannot make the browser fetch an arbitrary URL; blocked images render as an inert "Open image" link. Use this to show images from a trusted CDN inline, e.g. an image-generation provider
HERMES_WEBUI_SSE_CHUNKED
(unset)
Set truthy (1/true/yes/on) to send SSE with Transfer-Encoding: chunked. Needed behind buffering reverse proxies (e.g. jupyter-server-proxy) that otherwise buffer the whole stream; harmless but unnecessary for directly-served deployments
HERMES_WEBUI_EXTENSION_DIR
(unset)
Optional local directory served at /extensions/; must point to an existing directory before extension injection is enabled
HERMES_WEBUI_EXTENSION_MANIFEST
(unset)
Optional relative JSON manifest inside HERMES_WEBUI_EXTENSION_DIR listing bundled scripts/styles to inject; see WebUI Extensions
HERMES_WEBUI_EXTENSION_SCRIPT_URLS
(unset)
Optional comma-separated same-origin script URLs to inject; appended after manifest scripts; see WebUI Extensions
HERMES_WEBUI_EXTENSION_STYLESHEET_URLS
(unset)
Optional comma-separated same-origin stylesheet URLs to inject; appended after manifest stylesheets; see WebUI Extensions
HERMES_HOME
Windows: %LOCALAPPDATA%\hermes; POSIX: ~/.hermes
Base directory for Hermes state (affects all paths)
HERMES_CONFIG_PATH
$HERMES_HOME/config.yaml
Path to Hermes config file
HERMES_WEBUI_SERVER_CWD
(unset)
Working directory for the server process. Defaults to the agent dir; point it at a writable workspace when the agent dir is read-only so fallback relative writes land somewhere writable
HERMES_WEBUI_VISIBLE_SESSION_LIMIT
20
Size of the sidebar's interactive recency window (how many recent non-cron/webhook sessions are listed). Also bounds how many delegated subagent children can nest at once, since a child only renders when its row wins a slot in the window — raise it for wide fan-outs. Non-integer or non-positive values fall back to the default. Values above 200 are clamped. Resolved before profile init, so a profile .env cannot override it
HERMES_WEBUI_AGENT_CACHE_MAX
25
Max live agent instances kept warm in the in-memory LRU. Each pins a full conversation transcript, so this is the dominant lever on resident memory — lower it on installs with many long sessions to cap RAM (at the cost of more cold reloads)
HERMES_WEBUI_SESSIONS_MAX
100
Legacy operator override for the max compact Session objects held in the in-memory LRU. Prefer the webui.sessions_cache_max key in config.yaml (which takes precedence); this env var remains a fallback. Bounds resident memory so long-running installs cannot accumulate every session ever touched and eventually crash (#4765/#2233/#4633). Eviction only ever drops clean, persisted, non-active sessions; an evicted session lazily reloads from its JSON sidecar on next access
HERMES_WEBUI_RUN_JOURNAL_SWEEP
(unset)
Set to 0/false/off to disable the run-journal retention sweep entirely (#7613)
HERMES_WEBUI_RUN_JOURNAL_RETENTION_TTL_DAYS
14
Runs whose journal file is older than N days are archived (compressed into _run_journal_archive/, not deleted). 0 disables the age cap. Also settable via run_journal_retention_ttl_days in settings.json (the env var wins)
Keep at most N newest runs live per session; older runs are archived. 0 disables the count cap (run_journal_retention_max_runs_per_session in settings.json)
Per-session budget for LIVE run-journal bytes; sessions over budget archive their oldest runs. 0 disables the size cap (run_journal_retention_max_bytes_per_session in settings.json)
HERMES_WEBUI_RUN_JOURNAL_ARCHIVE_TTL_DAYS
0 (keep forever)
The only destructive knob: archives older than N days are deleted, except an archive a session still needs to recover an interrupted answer, which is kept until the session no longer references it or is deleted. 0 (default) never deletes archives — a stock install keeps every archived run forever (run_journal_archive_ttl_days in settings.json)
Run-journal retention (#7613)
The run journal stores one {run_id}.jsonl per run under sessions/_run_journal/<session_id>/; nothing removed them, so a long-lived session's journal grew without bound. An hourly sweep (piggybacked on the existing maintenance tick, never on a request path) now archives runs past the caps above rather than deleting them:
eligible runs are compressed (gzip) into sessions/_run_journal_archive/<session_id>/<run_id>.jsonl.gz — measured at 5–18% of the original size on real journals;
the compressed copy is verified to decompress to the exact original bytes before the live file is dropped;
runs that have not provably settled (no complete terminal row — including a journal truncated mid-write) are never touched;
a run the session still needs to recover an interrupted answer (its active stream, or the run an interrupted-turn marker names) stays live, so a release that predates the archive format can still recover it after a rollback;
every read path (run summaries, event reads, session replay, run lookup) transparently falls back to the archive, so a wrong classification costs one compressed copy, not the run;
deleting a session deletes its archives too.
Where dir_fd primitives are unavailable (Windows), the sweep disables itself rather than fall back to path-based moves a directory swap could redirect.
Extension deployments can inspect sanitized, authenticated diagnostics at GET /api/extensions/status; see WebUI Extensions.
Nix flake and NixOS module
Hermes WebUI has a Nix flake package and a NixOS service module so you can run it declaratively.
Install the latest package with:
nix shell github:nesquena/hermes-webui#default
Use this flake input in your system configuration:
The module defaults to 127.0.0.1. Set host = "0.0.0.0" and openFirewall = true only when you want direct network access, and pair that with auth, for example HERMES_WEBUI_PASSWORD via environmentFiles.
The published Hermes Agent package exposes passthru.hermesVenv, so the module derives HERMES_WEBUI_PYTHON from its interpreter. Bootstrap then locates the installed run_agent.py through that interpreter without importing Agent code and exports its parent as HERMES_WEBUI_AGENT_DIR. Packages may expose passthru.hermesAgentDir as a direct path instead. Use agent.dir and agent.python as explicit overrides for custom package layouts.
When WebUI reads shared Hermes Agent state, run the service as a user that can already read that state. For a co-located Hermes Agent service, set user and group to the agent service account; the module only creates the default hermes-webui account and never changes ownership of an existing hermesHome.
The module maps directly onto existing WebUI environment variables, including:
HERMES_WEBUI_HOST, HERMES_WEBUI_PORT, HERMES_WEBUI_STATE_DIR, HERMES_HOME, HERMES_WEBUI_AGENT_DIR, and HERMES_WEBUI_PYTHON.
Set environmentFiles for secrets like API keys. Protected WebUI runtime keys from the module are rejected there, so keep host, port, state, and agent wiring in the module options. Keep reverse proxy and TLS configuration in your surrounding deployment module because those details are deployment-specific.
Remote access (SSH tunnel, Tailscale, phone)
The server binds to 127.0.0.1 by default. To reach it from another machine,
use an SSH tunnel (ssh -N -L 8787:127.0.0.1:8787 user@host, which start.sh
prints for you over SSH) or, on a single-operator or access-restricted tailnet,
use the preferred Tailscale Serve
flow, which keeps WebUI on loopback behind tailnet-only HTTPS. Direct access to
http://<server-tailscale-ip>:8787 with HERMES_WEBUI_HOST=0.0.0.0 and
HERMES_WEBUI_PASSWORD is a fallback when Serve is unavailable. Full setup and
the community ARM64-Android field report: docs/remote-access.md.
Manual launch (without start.sh)
If you prefer to launch the server directly (for example from your own systemd unit):
export HERMES_WEBUI_AGENT_DIR=/path/to/hermes-agent # optional, see below
HERMES_WEBUI_PORT=8787 python3 /path/to/hermes-webui/server.py
Before importing anything else, server.py activates the Hermes Agent's dependency environment. It uses HERMES_WEBUI_AGENT_DIR when set, otherwise the same discovery start.sh uses ($HERMES_HOME/hermes-agent, ~/.hermes/hermes-agent, the hermes launcher, …), so the export is only needed for an Agent installed somewhere else. A Hermes-managed Agent (v0.21.6 or newer, installed by the official installer or hermes update) then restarts the server in its own Python with its own dependencies, so the interpreter you launch with does not need the Agent's packages. An older Agent that keeps its dependencies in venv/ or .venv/ is not restarted: run server.py with that venv's Python instead (/path/to/hermes-agent/venv/bin/python). System Python on its own lacks openai, httpx and other required packages.
Health check:
curl http://127.0.0.1:8787/health
Docker
Pre-built images (amd64 + arm64) are published to GHCR on every release.
For a comprehensive setup guide covering all 3 compose files, common failure modes, and bind-mount migration, see docs/docker.md. The README covers the 5-minute happy path.
5-minute quickstart (single container)
The simplest setup: one WebUI container that runs the agent in-process.
git clone https://github.com/nesquena/hermes-webui
cd hermes-webui
cp .env.docker.example .env
# Edit .env if your host UID isn't 1000 (e.g. macOS where UIDs start at 501)
docker compose up -d
# Open http://localhost:8787
Run Compose as the user who owns your Hermes home. sudo docker compose up -d can make ${HOME} expand to the root user's home, so Docker mounts the wrong .hermes directory instead of your real ~/.hermes and the WebUI starts with config.yaml (not found, using defaults). Prefer adding your user to the Docker group and running docker compose up -d; if you must use sudo, set absolute paths first, for example HERMES_HOME=/home/you/.hermes HERMES_WORKSPACE=/home/you/workspace sudo -E docker compose up -d, then verify with docker compose config.
The container auto-detects your UID/GID from the mounted ~/.hermes volume so files written by the agent stay readable by you on the host.
To enable password protection (required if you expose the port outside 127.0.0.1):
echo"HERMES_WEBUI_PASSWORD=change-me-to-something-strong">> .env
docker compose up -d --force-recreate
Both compose files use named Docker volumes by default, which solves the UID/GID problem by construction. If you need bind mounts to share an existing host directory, see docs/docker.md for the full migration recipe.
Known limitation (#681): in the two-container setup, tools triggered from the WebUI run in the WebUI container, not the agent container. If you need git/node/etc. on the WebUI's filesystem, either use the single-container setup, extend the WebUI Dockerfile, or use the community all-in-one image.
Source boundary note (#2453): the multi-container setup mounts hermes-agent-src read-only into the WebUI by default. This prevents WebUI-side source rewrites but is still an implementation-coupling bridge, not a stable Agent API boundary. See docs/rfcs/agent-source-boundary.md for the current source/API decoupling inventory.
Common failure modes
Symptom
Likely cause
Fix
PermissionError at startup
UID mismatch on bind mount
Set UID=$(id -u) in .env
.env: permission denied (#1389)
fix_credential_permissions() enforced 0600
Set HERMES_SKIP_CHMOD=1 in .env
Workspace appears empty
UID mismatch on /workspace mount
Set UID=$(id -u) in .env
git: command not found in chat
Two-container architectural limit (#681)
Use single-container or extend Dockerfile
WebUI can't find agent source
hermes-agent-src volume misconfigured
Use the named volumes from compose files as-is
Podman shared .hermes fails
Podman 3.4 keep-id limitation
Use Podman 4+ or single-container
Host API at localhost fails from WebUI
Container localhost means the container, not your host (#3012)
Use http://host.docker.internal:<port> on Docker Desktop, or http://host.containers.internal:<port> on Podman
WebUI can't see ~/.hermes after sudo docker compose
${HOME} expanded to the root user's home (#3006)
Run Compose as your user, or pass absolute HERMES_HOME/HERMES_WORKSPACE with sudo -E
Note: By default, Docker Compose binds to 127.0.0.1 (localhost only).
To expose on a network, change the port to "8787:8787" in docker-compose.yml
and set HERMES_WEBUI_PASSWORD to enable authentication.
Running tests
Tests discover the repo and the Hermes agent dynamically -- no hardcoded paths.
Use the repo test runner so local runs do not accidentally use an unsupported
system Python. It creates/uses .venv with Python 3.11, 3.12, or 3.13 and
installs the dev test dependencies from requirements-dev.txt when missing.
cd hermes-webui
./scripts/test.sh
Pass normal pytest arguments after the script for focused runs:
./scripts/test.sh tests/test_regressions.py -v
Or seed the repo .venv from an explicit supported base interpreter:
The override selects the Python used to create or rebuild .venv; dependencies
are still installed into the repo-local virtual environment, not into the
system/Homebrew interpreter.
Tests run against an isolated server with a separate state directory.
Production data and real cron jobs are never touched. Current snapshot:
~11,500 tests collected across ~1,150 test files, run in CI on Python 3.11,
3.12, and 3.13 (3 parallel shards each).
Architecture
No build step, no framework, no bundler — a Python standard-library HTTP server
and vanilla JS. The backend lives in api/, the frontend in static/.
Backend (api/)
server.py HTTP routing shell + auth middleware
api/
auth.py Optional password authentication, signed cookies, passkeys
config.py Discovery, globals, model detection, reloadable config
helpers.py HTTP helpers, security headers
models.py Session model + CRUD + CLI/state.db bridge
onboarding.py First-run onboarding wizard, OAuth provider support
profiles.py Profile state management, hermes_cli wrapper
routes.py All GET + POST route handlers (if/elif dispatch, no decorators)
state_sync.py /insights sync — message_count to state.db
streaming.py SSE engine, run_agent, cancellation, compression
updates.py Self-update check and release notes
upload.py Multipart parser, file upload handler
workspace.py File ops, workspace helpers, git detection
Frontend (static/)
index.html HTML template
style.css All CSS incl. mobile responsive, themes + skins
ui.js DOM helpers, renderMd, tool cards, context indicator
workspace.js File preview, file ops, git badge, central api() fetch wrapper
sessions.js Session CRUD, collapsible groups, search, reload recovery
messages.js send(), SSE handlers, live streaming, session recovery
panels.js Cron, skills, memory, profiles, settings (Control Center)
commands.js Slash command autocomplete
boot.js Mobile nav, voice input, theme/skin boot, bfcache handler
Tests + packaging
tests/ Pytest suite (~11,500 tests; isolated server/state fixtures)
pyproject.toml Standard build metadata plus the Ruff lint gate; checkout launch surface still centers on bootstrap.py / start.sh / ctl.sh
Dockerfile python:3.12-slim container image
docker-compose.yml Compose with named volume and optional auth
.github/workflows/ CI: ruff + sharded pytest, browser smoke, Docker smoke,
multi-arch Docker build + GitHub Release on tag
State lives outside the repo at ~/.hermes/webui/ by default
(sessions, workspaces, settings, projects, last_workspace). Override with HERMES_WEBUI_STATE_DIR.
Full design notes and the endpoint catalog are in ARCHITECTURE.md.
Compatibility
The version shown in the WebUI runtime status is the WebUI version only (build/image/tag currently running). It is not a full compatibility map.
The WebUI is still coupled to Hermes Agent internals for runtime execution, provider/model access, and state/schema usage until the stable agent boundary work in #1925 and #2491 land. In practice, the WebUI imports Agent modules directly (api/config.py, api/providers.py, api/streaming.py) and reads Agent state layout directly, so version skew can cause import or behavior drift.
Compatibility policy
WebUI release branches are tested against the matching Hermes Agent release available at that WebUI release time.
Upgrade both together: upgrade or pin WebUI and hermes-agent together (same release train/version/date), especially before enabling production traffic.
Running pinned older/newer combinations is untested and unsupported until the stable API boundary work in #1925 / #2491 is in place.
Record the full hermes-agent + hermes-webui versions in issue reports when upgrade mismatches are suspected.
Docker users: pin both image tags (or corresponding pinned source revisions) rather than using latest on one side and a fixed tag on the other. When upgrading the multi-container setup, follow the agent-image upgrade procedure in docs/docker.md (which requires dropping the hermes-agent-src volume before recreating). The current source-boundary status is tracked in docs/rfcs/agent-source-boundary.md.
Docs
Start here
docs/why-hermes.md — why Hermes, the mental model, and a detailed comparison to Claude Code / Codex / OpenCode / Cursor
docs/onboarding.md — first-run wizard, provider setup, local model server Base URLs, and safe re-runs
docs/troubleshooting.md — diagnostic flows for common failures (e.g. "AIAgent not available")
docs/kanban.md — the Kanban board's status flow: who may set which column, how tasks enter and leave Scheduled, and the parent re-gating on Scheduled/Blocked → Ready
docs/scripts-panel.md — the Tasks panel's Scripts subtab: where the profile's ~/.hermes/scripts/ directory comes from, the read-only endpoints, and the containment rules
Hermes WebUI is built with help from the open-source community. Every PR — whether merged directly, absorbed into a batch release, or salvaged from a larger proposal — shapes the project, and we're grateful to everyone who has taken the time to contribute.
Over 468 contributors have shipped code that landed in a release tag. The full, continuously-updated credit roll — including everyone with one or two PRs and the special-thanks roll for design and architectural work — lives in CONTRIBUTORS.md. A snapshot of the most prolific contributors:
Top contributors (by PR count, including absorbed/batch-released work)
See CONTRIBUTORS.md for the full ranked list of all 468 contributors — the 3+ PR tables, the 1–2 PR roll, and the special-thanks notes for design and architectural contributions.
Notable contributions
@franksong2702 — Most prolific external contributor (180 PRs, v0.49.3 → v0.51.384)
Across the longest tenure of any external contributor: the session title guard (#301), breadcrumb workspace navigation (#302), embedded workspace terminal (#1099), worktree-backed session creation (#2053), onboarding documentation (#2052), composer footer container queries, streaming-session sidebar exemption (#1327), session sidecar repair, cron output preservation (#1295), profile default workspace persistence, manual /compress async start/status endpoints (#2128), worktree status surface (#2109) + guarded remove (#2156) for the lifecycle umbrella #2057, session post-render dedup (#2166), native-WebUI fast path (#2170), tail-window response trim (#2171), stale-stream guard extension (#2158), CSP report collector (#2160), and a long tail of polish across mobile/responsive, the session sidebar, and the workspace state machine.
@Michaelyklam — Most prolific contributor of recent releases (118 PRs, v0.50.240 → v0.51.198)
Production Docker hardening (#1921, drops sudo-capable staging user), profile-scoped skills endpoints (#1903), gateway PID resolution under profile-scoped HERMES_HOME (#1901), profile-aware AIAgent cache (#1898/#1904), backslash LaTeX delimiters (#1848), Codex quota error surfacing (#1770), shell-route HTML 503 (#1836), stale Kanban client recovery (#1828), context auto-compression toast lifetime (#1988), /goal command (#1866), Kanban detail-view scrolling (#1916), CLI session tool metadata preservation (#1778), Traditional Chinese kanban locale backfill (#1979), v0.51.51 mobile Insights bucketing/layout (#2120/#2121), Hermes run adapter RFC (#2105 for #1925), fork-from-here absolute index (#2198 for #2184), opencode-go custom-provider overlap routing (#2204 for #1894).
@rodboev — Windows / cross-platform correctness + test reliability (83 PRs, v0.51.223 → v0.51.384)
A broad, sustained sweep with a strong focus on making the project work outside Linux: the ctl.sh Windows process-tree-kill fix (#3670), the local Windows full-suite signal/orphan-process work, slash-command autocomplete polish, and a long tail of frontend and infrastructure fixes shipped across dozens of release batches.
@bergeouss — Provider management UI + Docker hardening (70 PRs, v0.48.0 → v0.51.385)
Provider management UI for adding/editing custom providers from Settings, OAuth provider status detection (#1552), two-container Docker setup, profile isolation hardening (per-profile .env secrets), the bulk of what users see when they touch Settings → Providers, Reveal-in-Finder context menu (#1551), gateway status card (#1552), auto-assign session to active project filter (#1550), "What's new?" link in update banner (#1549), OpenRouter free-tier live fetch (#1548), credential pool 401 self-heal (#1553), inline provider chip + group model count in model picker (#1644).
@dso2ng — Session lineage + diagnostics (30 PRs, v0.50.227 → v0.51.327)
/api/session/lineage-report/<sid> endpoint for bounded session graph diagnostics (#2012), stale Mermaid render error cleanup (#1337), session_source="fork" continuation-chain isolation (#2063), lazy lineage-report fetch on sidebar badge expand (#2130), and a long tail of frontend reliability fixes around session loading.
@jasonjcwu — Composer + transcript polish (16 PRs, v0.50.227 → v0.51.132)
Sidebar collapse via active-rail click (#2054, fuses #1884 + #1924), composer chip lightbox (#1758), title fixes for tool-heavy first turns, silent compress-status during session switch (#2185), concurrent-send loss fix (#2186), in-transcript steer message badges (#2187), and a string of frontend polish fixes.
@Jordan-SkyLF — Live streaming + UX polish (12 PRs, v0.50.18 → v0.51.66)
Original sprint of workspace fallback resolution, live reasoning cards (#366, #367, #394–#397), then a recent burst: manual "Refresh usage" button on the Provider quota card (#2150), cancelled-turn status classification (#2151), Firefox sidebar scroll stabilization (#2200), early provisional session titles (#2202), target-aware "What's new?" update-banner links (#2207), and MCP tools overflow fix in Settings (#2210).
@aronprins — v0.50.0 UI overhaul (PR #242, plus 9 follow-ups)
The biggest single contribution to the project: a complete UI redesign that moved model/profile/workspace controls into the composer footer, replaced the gear-icon settings panel with the Hermes Control Center (tabbed modal), removed the activity bar in favor of inline composer status, redesigned the session list with a ⋯ action dropdown, and added the workspace panel state machine. Plus chat transcript redesign (#587), sidebar declutter (#584), three-column layout refactor (#899), light/dark theme + accent skins (#627), and shared confirm()/prompt() dialog replacement (PR #251 extracted from #242).
@iRonin — Security hardening sprint (PRs #196–#204)
Six consecutive, focused security PRs: session memory leak fix (expired token pruning), CSP + Permissions-Policy headers, 30-second slow-client connection timeout, optional HTTPS/TLS support via environment variables, upstream branch tracking fix for self-update, and CLI session support in the file-browser API. The kind of focused, high-quality security work that makes a self-hosted tool trustworthy.
@lucasrc — Auth-hardening trilogy (PRs #2191, #2192, #2193)
Three coordinated security PRs that all landed in v0.51.57: thread-safe login rate limiter with PBKDF2 key separation, password-hash cache invalidation on Settings save, and the full 64-char HMAC-SHA256 session signature with a backwards-compatible migration bridge. The kind of cleanly-decomposed security work that's reviewable as three independent pieces.
@LumenYoung — Streaming hot-path correctness (8 PRs, v0.51.47 → v0.51.99)
The original stale-stream writeback guard (#2136 — the bug class the next two releases extended), gateway-state alive-null classification (#2075), compression-banner anchor alignment (#2182), and context-progress ring auto-refresh on compression complete (#2188). Each PR opened a small surgical fix in one of the most fragile subsystems in the codebase.
@dobby-d-elf — Frontend reliability + motion polish (15 PRs, v0.51.38 → v0.51.161)
Workspace fallback on deleted directories (#2138), iPhone PWA bottom-scroll fix (#2143), the new "Activity: X tools" composer footer shimmer animation (#2203), and follow-up animation tuning (#2212).
@JKJameson — Composer + session polish (10 PRs)
Persistent composer draft per session (#1956), and a long tail of polish across the composer and session sidebar.
@gabogabucho — Spanish locale + onboarding wizard
Full Spanish (es) locale covering all UI strings, plus the one-shot bootstrap onboarding wizard that guides new users through provider setup on first launch.
@deboste — Reverse-proxy auth + mobile responsive layout (PRs #3, #4, #5)
Three of the very first community PRs: fixed EventSource/fetch to use URL origin for reverse-proxy setups, corrected model provider routing from config, and added mobile responsive layout with dvh viewport fix. Early foundation work.
@indigokarasu — Visual redesign proposal (PR #213)
A CSS-only redesign of the full UI — proper design tokens, an icon rail sidebar replacing the emoji tab strip, consistent form cards, breadcrumb nav, and 7 built-in themes as custom properties. The PR didn't merge as-is but shaped the design language and theme architecture that shipped in v0.50.0.
@zenc-cp — Anti-hallucination guard for the ReAct loop (PR #133)
A three-layer approach (ephemeral anti-hallucination prompt, live token filtering, session-history cleanup) that the streaming pipeline still uses.
@Hinotoi-agent — Profile + session security (PRs #351, #2048)
Profile .env secret isolation fix (PR #351) preventing API key leakage between profiles, and session-import workspace validation (PR #2048) blocking a crafted-JSON file-read against /.
@Sanjays2402 — Endless-scroll + Start-jump race fix (PR #1949)
A generation-token + mutex pair fixing the v0.51.30 race between endless-scroll prefetch and Start-jump's _ensureAllMessagesLoaded. The naive same-flag-check approach (proposed in #1942 and #1962) was a no-op for the post-await race — Sanjays2402's fix was the correct shape.
@fxd-jason — Real-time approval + clarify via SSE (PRs #1350, #1355)
Replaced 1.5s HTTP polling with SSE long-connections for both approval and clarify, cutting latency from up to 1.5s to near-instant. Got all the correctness details right (atomic subscribe + snapshot, notify-inside-lock, head-of-queue payload, trailing event re-emission).
@happy5318 — Custom provider model dedup (PR #1947)
Fixed the same model from different named custom providers being silently deduplicated in the picker, with Opus catching a race in the original tests that needed augmentation.
@NocGeek — Streaming scroll + manual cron output persistence (7 PRs)
Streaming scroll viewport stability when tool/queue cards insert (#1360), manual cron-run output and metadata persistence (#1372, split from held #1352).
@DavidSchuchert — German translation (PR #190)
Complete German locale (de) covering all UI strings, settings labels, commands, and system messages — and stress-tested the i18n system, exposing several elements that weren't yet translatable and getting them fixed as part of the same PR.
@Bobby9228 — Mobile Profiles button (PR #265)
Added the Profiles entry to the mobile navigation flow, making profile switching reachable on phones.
@kevin-ho — OLED theme (PR #168)
The 7th built-in theme: pure black backgrounds with warm accents tuned to reduce burn-in risk.
@andrewy-wizard — Chinese localization (PR #177)
Initial Simplified Chinese (zh) locale. One of the first non-English locales.
@DelightRun — session_search fix for WebUI sessions (PR #356)
Tracked down the missing SessionDB injection in the streaming path that was silently breaking the tool for every WebUI session.
@lawrencel1ng — Bandit security fixes (PR #354)
Systematic bandit-scan fixes: URL scheme validation before urlopen, MD5 usedforsecurity=False, and 40+ bare except: pass blocks replaced with proper logging.
@shaoxianbilly — Unicode filename downloads (PR #378)
Proper Content-Disposition with RFC 5987 filename*=UTF-8''... encoding so non-ASCII filenames download without crashing.
@lx3133584 — CSRF fix for reverse proxy (PR #360)
A real-world blocker for anyone hosting behind Nginx Proxy Manager or similar on a port other than 80/443.
@betamod — Security audit (PR #171)
A comprehensive CSRF / SSRF / XSS / env-race-condition audit that shipped in v0.39.0.
@TaraTheStar — Bot name + thinking blocks + login refactor (PRs #132, #176, #181)
Configurable assistant display name, thinking/reasoning block display, and a login page refactor.