Academy → Using HermesOfficial documentation · clear explanation

Tools & Toolsets

الأدوات & Toolsets

Essential13 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Tools & Toolsets as part of operating Hermes with explicit security boundaries. 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 Available Tools, Using Toolsets, Terminal Backends, then verify failure modes and version compatibility.

What do you need first?

You only need to know which files and accounts the agent may access.

What will you know?

A clear outcome before you read.

  • Understand Tools & Toolsets 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.
Lesson terms

Short definitions before the details.

Tool
A structured action the agent can call to read or change something.
Approval & sandbox
Approval pauses a sensitive action before execution; sandboxing limits impact if something goes wrong.
Official page description

Overview of Hermes Agent's tools — what's available, how toolsets work, and terminal backends

Topic map

What does the source say, and in what order?

  1. 01
    Available Tools

    Start here to understand the core idea or structure.

  2. 02
    Using Toolsets

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

  3. 03
    Terminal Backends

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

  4. 04
    Configuration

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

  5. 05
    Shell startup files and non-interactive commands

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

  6. 06
    Docker Backend

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

  7. 07
    SSH Backend

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

  8. 08
    Singularity/Apptainer

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

  9. 09
    Modal (Serverless Cloud)

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

  10. 10
    Vercel Sandbox

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

# Use specific toolsets hermes chat --toolsets "web,terminal" # See all available tools hermes tools # Configure tools per platform (interactive) hermes tools
# In ~/.hermes/config.yaml terminal: backend: local # or: docker, ssh, singularity, modal, daytona, vercel_sandbox cwd: "." # Working directory timeout: 180 # Command timeout in seconds
# ~/.bashrc — keep this guard near the top case $- in *i*) ;; # interactive: continue *) return;; # non-interactive: stop here esac # heavy/interactive init goes BELOW the guard export NVM_DIR="$HOME/.nvm" [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
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 “Tools & Toolsets” 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?