v0.6.15 · self-hosted runtime

Local control plane for coding agents.

Chat with Hermes Agent, manage profiles, launch coding sessions, inspect files, run jobs, and keep every runtime decision inside your own workspace.

Download Desktop Read Docs

7,953GitHub stars

Profilesisolated models, jobs, files

Localdesktop + web runtime

profile: openai-prod · agent: hermes

Workspace run npm install -g hermes-web-ui

Agent thread streaming

Hermes can keep the chat, file tree, command trace, model context, and downloads together instead of scattering agent work across terminal tabs.

Compress context before the next coding session

Preview release assets before promotion

Route mentions into a multi-agent room

Runtime map local

Profiles keep credentials, skills, providers, jobs, uploads, and visibility separate. The dashboard becomes an operator surface, not just a chat window.

OpenAI-compatible providers

Web terminal over PTY

Docker, SSH, local file backends

release0.6.15

installDMG / EXE / AppImage

licenseBSL-1.1

stackVue 3 + TS

Workflow

One surface for the agent loop.

The page should sell the operating loop first: start an agent, watch tool traces, move through files and terminal output, then promote the result into repeatable jobs.

Start with chat

Streaming sessions, markdown, uploads, downloads, model badges, and context usage stay attached to the conversation.

Scope by profile

Credentials, providers, memory, jobs, uploads, and visibility are isolated per Hermes profile.

Operate the workspace

Files, PTY terminal, Docker, SSH, and local backends sit beside the agent instead of in another tool.

Automate repeat work

Cron jobs, immediate runs, Kanban state, and usage analytics turn one-off agent work into an operational system.

Product

Show fewer things, with sharper proof.

Instead of twelve equal cards, group the strongest capabilities around what a self-hosted agent operator actually does every day.

Agent chatSessions, tool traces, uploads, downloads, markdown, model badges, and context usage.

ProfilesSeparate config, credentials, skills, plugins, providers, jobs, memory, and visibility.

Files + terminalBrowse and edit files across local, Docker, SSH, and Singularity backends with a browser PTY.

Jobs + analyticsSchedule runs, track cost, token usage, cache hit rates, and model distribution over time.

Install

One recommended path first. Everything else after.

The original download section asks users to choose too early. This version detects the main path, keeps the npm command visible, and still exposes every release asset.

v0.6.15

macOS Apple SiliconHermes.Studio-0.6.15-arm64.dmg GitHub Cloudflare

Windows x64Hermes.Studio-0.6.15-x64.exe GitHub Cloudflare

Linux x64AppImage or Debian package Release AppImage

Self-hosted web UInpm install -g hermes-web-ui npm Docs

Trust

Make the self-hosted promise explicit.

For this audience, trust is product value. The site should say what stays local, what is profile-scoped, how releases are distributed, and what the license means.

Local runtime

Desktop builds bundle the Studio runtime and keep Studio state separate from Hermes Agent data.

Profile isolation

Models, providers, uploads, jobs, skills, plugins, memory, and access can be separated by profile.

Release clarity

Cloudflare is the fast download path, GitHub is the fallback and canonical release record.