Power Hermes with your local model
Point Hermes at your LM Studio server with two config lines
Hermes is a personal AI assistant you install locally (covered in the Hermes course). It needs a model to think with — by default you point it at a cloud provider, but pointing it at LM Studio instead means Hermes runs entirely on your machine: zero cloud calls, zero per-token cost, full privacy. This lesson is the bridge between the two courses. If you have not installed Hermes yet, do this lesson anyway — the config steps are the same whenever you are ready.
- 1 Make sure LM Studio's server is running (Developer tab → Start Server, or
lms server start). Check that a model is loaded. - 2 Open
~/.hermes/config.yamlin any text editor. (If the file does not exist, runhermes setupfirst — see the Hermes course, lesson hermes-00.) - 3 Set these two lines:
`yaml provider: custom base_url: "http://localhost:1234/v1"`Save the file. - 4 Add a placeholder API key — open
~/.hermes/.envand add (or confirm the presence of):`OPENAI_API_KEY=local`Local servers ignore the key value; Hermes still needs the variable to be set. - 5 Start Hermes: run
hermes --tuiin a terminal, or open Hermes Desktop. Type:What model are you running on?— it should identify the LM Studio model you have loaded. - 6 Optional — use a model on another machine on your LAN. Replace
localhostwith that machine's IP, e.g.base_url: "http://192.168.1.42:1234/v1". LM Studio must be bound to the network interface on that machine (see lesson lmstudio-04).
Hermes responds from your local LM Studio model. No internet connection is required for the conversation to work.
Compare local vs cloud Hermes on a real task
Switching between a local and a cloud model in Hermes is a two-line config change. Use that to find where the local model is good enough and where you need the cloud.
Run the same Hermes task twice — once with LM Studio, once with a cloud provider — and decide which you would use for each kind of job in your research.
- 1 With LM Studio active, give Hermes a research task:
Search for recent papers on [your topic] and summarise three key findings. - 2 Switch
config.yamlto a cloud provider (anthropic, openai, or openrouter) and repeat the exact same task. - 3 Compare quality, speed, and what left your machine.
- 4 Write a one-sentence rule for your own use: 'I will use local for X and cloud for Y.'
Both outputs side by side and your one-sentence local-vs-cloud rule.