CLI Commands Reference
مرجع أوامر CLI
Start with meaning, then move to detail.
This lesson explains CLI Commands Reference as part of using Hermes through messaging channels. 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 Global entrypoint, Global options, Top-level commands, then verify failure modes and version compatibility.
Prepare the channel account and understand allowlists and secret storage.
A clear outcome before you read.
- Understand CLI Commands Reference 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.
- Gateway
- The process that connects Hermes to channels such as Telegram or Discord and routes messages.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
Authoritative reference for Hermes terminal commands and command families
What does the source say, and in what order?
- 01Global entrypoint
Start here to understand the core idea or structure.
- 02Global options
Read this after the foundation, then connect it to the previous step.
- 03Top-level commands
Read this after the foundation, then connect it to the previous step.
- 04hermes chat
Read this after the foundation, then connect it to the previous step.
- 05hermes -z <prompt> — scripted one-shot
Read this after the foundation, then connect it to the previous step.
- 06--usage-file — JSON usage report for pipelines
Read this after the foundation, then connect it to the previous step.
- 07hermes model
Read this after the foundation, then connect it to the previous step.
- 08/model slash command (mid-session)
Read this after the foundation, then connect it to the previous step.
- 09hermes gateway
Read this after the foundation, then connect it to the previous step.
- 10hermes lsp
Finish here to verify the result and special cases.
Copy only after you understand the effect.
hermes [global-options] <command> [subcommand/options]hermes chat [options]hermes
hermes chat -q "Summarize the latest PRs"
hermes chat --provider openrouter --model anthropic/claude-sonnet-4.6
hermes chat --toolsets web,terminal,skills
hermes chat --quiet -q "Return only JSON"
hermes chat --worktree -q "Review this repo and open a PR"
hermes chat --ignore-user-config --ignore-rules -q "Repro without my personal setup"
hermes chat --safe-mode -q "Is this bug mine or Hermes'?"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.