Slash Commands Reference
Slash Commands Reference
Start with meaning, then move to detail.
This lesson explains Slash Commands Reference as part of extending Hermes and connecting external tools. 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 Permissions and admin/user split, Interactive CLI slash commands, Session, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Slash 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.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
- Tool
- A structured action the agent can call to read or change something.
Complete reference for interactive CLI and messaging slash commands
What does the source say, and in what order?
- 01Permissions and admin/user split
Start here to understand the core idea or structure.
- 02Interactive CLI slash commands
Read this after the foundation, then connect it to the previous step.
- 03Session
Read this after the foundation, then connect it to the previous step.
- 04Configuration
Read this after the foundation, then connect it to the previous step.
- 05Tools & Skills
Read this after the foundation, then connect it to the previous step.
- 06Info
Read this after the foundation, then connect it to the previous step.
- 07Exit
Read this after the foundation, then connect it to the previous step.
- 08Dynamic CLI slash commands
Read this after the foundation, then connect it to the previous step.
- 09Quick Commands
Read this after the foundation, then connect it to the previous step.
- 10Custom model aliases
Finish here to verify the result and special cases.
Copy only after you understand the effect.
quick_commands:
status:
type: exec
command: systemctl status hermes-agent
deploy:
type: exec
command: scripts/deploy.sh
inbox:
type: alias
target: /gmail unreadmodel_aliases:
fav:
model: claude-sonnet-4.6
provider: anthropic
grok:
model: grok-4
provider: x-ai
ollama-qwen:
model: qwen3-coder:30b
provider: custom
base_url: http://localhost:11434/v1hermes config set model.aliases.fav anthropic/claude-opus-4.6
hermes config set model.aliases.grok x-ai/grok-4Read 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.