Academy → Using HermesOfficial documentation · clear explanation

Wake Word

Wake Word

Beginner to advanced15 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Wake Word as part of using Hermes and understanding its behavior. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

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 hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect How it works, Remote desktop (client capture), Engines, then verify failure modes and version compatibility.

What do you need first?

Start with installation if you have not run Hermes yet.

What will you know?

A clear outcome before you read.

  • Understand Wake Word 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.
Official page description

Hands-free 'Hey Hermes' wake word — start a voice session by speaking, the 'Hey Siri' way

Topic map

What does the source say, and in what order?

  1. 01
    How it works

    Start here to understand the core idea or structure.

  2. 02
    Remote desktop (client capture)

    Read this after the foundation, then connect it to the previous step.

  3. 03
    Engines

    Read this after the foundation, then connect it to the previous step.

  4. 04
    Quick start

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Configuration

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Reducing false triggers on ambient speech

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Surfaces (CLI, TUI, GUI)

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Using a different phrase

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Option A — sherpa (any phrase, zero training)

    Read this after the foundation, then connect it to the previous step.

  10. 10
    Waking a specific profile (desktop)

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

wake_word: enabled: true capture: auto # auto | local | client # auto — local PortAudio unless the desktop arms with client_capture # local — always open the backend mic (CLI/TUI default) # client — always expect wake.feed PCM from the desktop (remote-friendly)
cd ~/.hermes/hermes-agent && uv pip install -e ".[wake]"
# In an interactive `hermes` session: /wake on # start listening (installs the engine on first use) /wake status # show phrase, provider, and state /wake off # stop listening
Try it now

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.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Wake Word” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?