20fd0bde5d
* feat(desktop): surface TTS/STT/terminal backends as Settings dropdowns Every native tool backend that the agent supports now shows up as a clickable picker in the desktop Settings UI instead of a free-text box. Desktop Settings renders a config field as a <Select> only if its dotpath is a key in ENUM_OPTIONS (helpers.ts::enumOptionsFor returns undefined -> free-text <Input> otherwise). Three backend-selector fields were surfaced in their sections but missing from the map, so users had to hand-type the provider name and could reasonably assume it was unsupported: - tts.provider — now lists all built-in TTS backends incl. xai (Grok) - stt.provider — local/groq/openai/mistral/elevenlabs - terminal.backend — local/docker/singularity/modal/daytona/ssh Each list is kept in sync with its backend source of truth (TTS: agent/tts_registry.py::_BUILTIN_NAMES + tools/tts_tool.py; STT + terminal: hermes_cli/config.py / tools/terminal_tool.py). The existing enumOptionsFor current-value-append keeps any hand-typed/legacy value selected, and command-type TTS providers still work. Reported for Grok/xAI TTS, which was already a fully-wired built-in provider (tts.provider: xai + XAI_API_KEY) with no picker entry. * feat(desktop): expose per-backend TTS/STT/terminal config fields in Settings Completes the backend-coverage pass: not just the provider PICKER but every backend's own config fields are now tunable from desktop Settings, so a user who picks (e.g.) Grok TTS can also set its voice/language without hand-editing config.yaml. Also fixes the STT provider dropdown: added 'xai' (Grok STT), which the transcription dispatcher (tools/transcription_tools.py) handles but the config.py comment had omitted — the dispatch ladder is the source of truth. New Settings fields (Voice section): - TTS xai (voice_id, language), minimax (model, voice_id), mistral (model, voice_id), gemini (model, voice), neutts (model, device), kittentts (model, voice), piper (voice) - STT openai (model), groq (model), mistral (model) New Settings fields (Advanced section): - terminal docker_image / singularity_image / modal_image / daytona_image New ENUM_OPTIONS dropdowns: stt.provider (+xai), stt.openai.model, stt.mistral.model, tts.openai.model, tts.elevenlabs.model_id, tts.neutts.device. Each list mirrors the backend generator's accepted values (tools/tts_tool.py, tools/transcription_tools.py, hermes_cli/config.py). i18n: FIELD_LABELS/FIELD_DESCRIPTIONS cover all locales via the English fallback in config-settings.tsx; added native translations to ja/zh/zh-hant. Secrets (provider API keys, modal/daytona tokens, ssh host/key) intentionally stay in Settings -> Keys as env vars, not duplicated as config fields. |
||
|---|---|---|
| .. | ||
| assets | ||
| electron | ||
| public | ||
| scripts | ||
| src | ||
| .prettierrc | ||
| components.json | ||
| DESIGN.md | ||
| eslint.config.mjs | ||
| index.html | ||
| package.json | ||
| preview-demo.html | ||
| README.md | ||
| tsconfig.json | ||
| vite.config.ts | ||
Hermes Desktop ☤
The native desktop app for Hermes Agent — the self-improving AI agent from Nous Research. Same agent, same skills, same memory as the CLI and gateway, in a polished native window — chat with streaming tool output, side-by-side previews, a file browser, voice, and settings, no terminal required. Available for macOS, Windows, and Linux.
| Chat with the full agent | Streaming responses, live tool activity, structured tool summaries, and the same conversation history as every other Hermes surface. |
| Side-by-side previews | Render web pages, files, and tool outputs in a right-hand pane while you keep chatting. |
| File browser | Explore and preview the working directory without leaving the app. |
| Voice | Talk to Hermes and hear it back. |
| Settings & onboarding | Manage providers, models, tools, and credentials from a real UI. First-run setup gets you to your first message in seconds. |
| Stays current | Built-in updates pull the latest agent and rebuild the app in place. |
Install
Install with Hermes (recommended)
Already have the Hermes CLI? Just run:
hermes desktop
It builds and launches the GUI against your existing install — same config, keys, sessions, and skills. On first launch Hermes walks you through picking a provider and model; nothing else to configure.
Prebuilt installers
Prebuilt installers are built and distributed via the Hermes Desktop website..
Updating
The app checks for updates in the background and offers a one-click update when one is ready. You can also update any time from the CLI:
hermes update
Requirements
The installer handles everything for you (Python 3.11+, a portable Git, ripgrep).
Development
Want to hack on the app itself? Install workspace deps from the repo root once, then run the dev server from this directory:
npm install # from repo root — links apps/desktop, web, apps/shared
cd apps/desktop
npm run dev # Vite renderer + Electron, which boots the Python backend
Point the app at a specific source checkout, or sandbox it away from your real config:
HERMES_DESKTOP_HERMES_ROOT=/path/to/clone npm run dev
HERMES_HOME=/tmp/throwaway npm run dev
npm run dev:fake-boot # exercise the startup overlay with deterministic delays
Building installers
npm run dist:mac # DMG + zip
npm run dist:win # NSIS + MSI
npm run dist:linux # AppImage + deb + rpm
npm run pack # unpacked app under release/ (no installer)
Installers are built and uploaded to GitHub Releases manually. macOS/Windows signing & notarization happen automatically when the relevant credentials are present in the environment (CSC_LINK / CSC_KEY_PASSWORD / APPLE_* for macOS, WIN_CSC_* for Windows).
How it works
The packaged app ships only the Electron shell. On first launch it installs the Hermes Agent runtime into HERMES_HOME (~/.hermes, or %LOCALAPPDATA%\hermes on Windows) — the same layout a CLI install uses, so the two are interchangeable. The renderer (React, in src/) talks to a hermes dashboard backend over the standard gateway APIs and reuses the embedded TUI rather than reimplementing chat. The install, backend-resolution, and self-update logic all live in electron/main.cjs.
Verification
Run before opening a PR (lint may surface pre-existing warnings but must exit cleanly):
npm run fix
npm run type-check
npm run lint
npm run test:desktop:all
Troubleshooting
Boot logs land in HERMES_HOME/logs/desktop.log (includes backend output and recent Python tracebacks) — check it first if the app reports a boot failure.
macOS / Linux:
# Force a clean first-launch setup
rm "$HOME/.hermes/hermes-agent/.hermes-bootstrap-complete"
# Rebuild a broken Python venv
rm -rf "$HOME/.hermes/hermes-agent/venv"
# Reset a stuck macOS microphone prompt (macOS only)
tccutil reset Microphone com.nousresearch.hermes
Windows (PowerShell):
# Force a clean first-launch setup
Remove-Item "$env:LOCALAPPDATA\hermes\hermes-agent\.hermes-bootstrap-complete"
# Rebuild a broken Python venv
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\hermes\hermes-agent\venv"
The default Hermes home on Windows is
%LOCALAPPDATA%\hermes. Set theHERMES_HOMEenv var if you've relocated it.
Community
- 💬 Discord
- 📖 Documentation
- 🐛 Issues
License
MIT — see LICENSE.
Built by Nous Research.