Desktop App
Desktop App
Start with meaning, then move to detail.
This lesson explains Desktop App as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Install, What's in the app, Chat, then verify failure modes and version compatibility.
No prior experience is required; follow the steps on a safe test setup first.
A clear outcome before you read.
- Understand Desktop App without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Provider
- The service that runs or provides access and authentication to a model.
- Browser / CDP
- A layer for programmatic browser control and page or event inspection.
The native Hermes desktop app — a polished experience for chatting with Hermes, with streaming tool output, side-by-side previews, a file browser, voice, cron, profiles, skills, and settings. macOS, Windows, and Linux.
What does the source say, and in what order?
- 01Install
Start here to understand the core idea or structure.
- 02What's in the app
Read this after the foundation, then connect it to the previous step.
- 03Chat
Read this after the foundation, then connect it to the previous step.
- 04Status bar
Read this after the foundation, then connect it to the previous step.
- 05Repository discovery
Read this after the foundation, then connect it to the previous step.
- 06Choosing a model
Read this after the foundation, then connect it to the previous step.
- 07File browser
Read this after the foundation, then connect it to the previous step.
- 08Artifacts
Read this after the foundation, then connect it to the previous step.
- 09Windows, tabs & panes
Read this after the foundation, then connect it to the previous step.
- 10Terminal
Finish here to verify the result and special cases.
Copy only after you understand the effect.
hermes desktopdesktop:
repo_scan_enabled: true
repo_scan_roots: []
repo_scan_exclude_paths: []# 1. Set the dashboard login credentials.
cat >> ~/.hermes/.env <<'EOF'
HERMES_DASHBOARD_BASIC_AUTH_USERNAME=admin
HERMES_DASHBOARD_BASIC_AUTH_PASSWORD=choose-a-strong-password
# Recommended: a stable signing secret so sessions survive restarts.
# Without it a random key is generated per boot and you'll be logged out
# on every restart.
HERMES_DASHBOARD_BASIC_AUTH_SECRET=$(openssl rand -base64 32)
EOF
chmod 600 ~/.hermes/.env
# 2. Run the backend bound to a reachable address. The non-loopback bind
# engages the auth gate; the username/password provider handles login.
hermes serve --host 0.Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.