How-To Series · Episode 11 / 59 · Module 2: Daily Driver

Hermes · Tools & Toolsets

What the agent can do · grouped into toolsets · togglable per platform.

After this videoYou can now give each surface exactly the tools it needs — and sandbox the terminal.

Tools are verbs. Toolsets are groups of verbs. hermes tools is the interactive control panel: toggle per platform so your CLI gets everything and your Telegram bot gets only what's safe to expose. --toolsets "web,terminal" is the per-run override. The terminal backend is the big safety knob — local for trusted dev, docker for a persistent sandboxed container, ssh if you want the agent on a different machine than its own source. Containers come hardened by default (read-only root, no Linux capabilities, 256-PID limit).

About these resources. Every command and config in this video comes from the Tools & Toolsets user-guide doc. The Configuration page is cited for the Docker-backend persistent-container lifecycle details.

Sources · What this video distills

2 docs pages · every command below traces to one of them
Primary · the tool registry, hermes tools, --toolsets, terminal backends, container hardening, Tool Gateway
Tools & Toolsets
Read ↗
Docker backend lifecycle and container_persistent flag
Configuration · Docker backend
Read ↗

Commands shown · Copy and paste

each shows the source doc it came from
Interactive control panel (per-platform toggles)from Tools & Toolsets ↗
hermes tools
Per-run override · just this sessionfrom Tools & Toolsets ↗
hermes chat --toolsets "web,terminal"
Pick a terminal backendfrom Tools & Toolsets ↗
hermes config set terminal.backend docker
Real isolation · run commands on a remote boxfrom Tools & Toolsets ↗
hermes config set terminal.backend ssh

Going deeper · Related Hermes docs

further reading · not sources of facts shown above

Next in the series · Episodes that build on this

E20
Browser Automation
E21
Web Search · Tool Gateway
E32
Cron Jobs