Install Hermes Desktop
Download, complete setup, obtain one chat reply. Leave Advanced settings for later.
Module 03 target · real labels may move — docs win
You need
- ·A PC you control (Windows or macOS; Linux Desktop if offered for your build)
- ·Network for download and one model provider
Install Desktop
Later modules assume this cockpit: chat, profiles, tools, approvals, gateway, and cron.
Settings map (inspect, then leave defaults)
After chat works, open Settings once to learn the layout, then close without changing Advanced defaults.
- ·Providers / models — APIs, local endpoints, routing
- ·Gateway / messaging — Telegram and other surfaces (module 05)
- ·Advanced — terminal backend, Docker, isolation (not required for Part I proofs)
Stabilize one provider
Choose one model provider you can call reliably, then stop. Do not debug gateway, Docker, and authentication in parallel.
Where your files live
Desktop stores the harness on disk (Hermes home — often ~/.hermes or under user AppData). Each profile is an isolated home. Back up by copying folders; the same files can move later to another host.
Optional companions
IDE-shaped coding agents are optional. This course’s home base is Hermes; add companions only after the harness works.
After this proof
Install is complete here. Ops drills (Desktop checklist, key rotation, extra models) belong in Harness Labs — after this proof, not instead of it.
Hermes Desktop is open, setup is finished, one chat reply works, and Advanced/Docker was left at defaults.
Stored on this device only — not sent anywhere.