Desktop App
The Hermes desktop app is a native app built around the same agent you get from the CLI and the gateway — same config, same API keys, same sessions, same skills
- Section
- Using Hermes
- Source
- hermesbible.com/docs/user-guide/desktop
The Hermes desktop app is a native app built around the same agent you get from the CLI and the gateway — same config, same API keys, same sessions, same skills
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- Install
- What's in the app
- Chat
- Status bar
- Choosing a model
- File browser
- Voice
- Settings & onboarding
- Management panes
- Keyboard & navigation
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
Section map
Install
Maps install to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
What's in the app
Maps what's in the app to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Chat
Maps chat to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
File browser
Maps file browser to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Voice
Maps voice to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Settings & onboarding
Maps settings & onboarding to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Management panes
Maps management panes to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Keyboard & navigation
Maps keyboard & navigation to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Using Hermes doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
- Primary decision areas: Install, What's in the app, Chat, File browser, Voice. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: desktop, native, around, gateway, config. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for desktop app before applying exact upstream commands.
Open the source anchor for Install and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Using Hermes, then open the linked source page for exact current syntax.
- Start with the source section for Install; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for What's in the app if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.
Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.
Set provider, token, and retry limits before scaling the workflow beyond a single test run.
Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.
What this page covers
- Core concept and where it fits in the Hermes Agent system.
- Setup or operating context implied by the upstream page summary.
- The source page link for full current details and updates.
Source mirror note
This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.
Open source page