HeyRocky

Toolsets Overview

What this page covers

Toolsets are how Hermes exposes capabilities safely. Tools are grouped into categories such as web, terminal, file, browser, vision, image generation, TTS, skills, memory, session search, cron, delegation, and messaging, and they can be enabled per platform.

Hermes changes quickly, so treat the official documentation as the source of truth and use the built-in CLI to inspect the local install before editing config by hand.

Fast path

```bash

hermes tools

```

```bash

hermes tools list

```

```bash

hermes tools enable web

hermes tools disable browser

```

```bash

hermes chat --toolsets "web,terminal" -q "Search the web, then summarize the result."

```

Practical checklist

  • Enable only the capabilities needed for the surface: CLI, gateway, cron, or locked-down safe mode.
  • Use `terminal` and `file` for local development; add `web`/`browser` only when current public information or live UI verification is required.
  • Use the `safe` toolset for low-risk sessions where network, shell, or broad file access should not be exposed.
  • Remember that dynamic MCP tools appear as MCP-specific toolsets once configured.
  • Start a new session after changing platform toolsets.

Common pitfalls

  • Turning on browser, terminal, and messaging everywhere without a reason.
  • Expecting a disabled tool to be available because it was enabled in another profile or platform.
  • Forgetting that Docker/remote terminal backends also affect file tools.

Verification checklist

  • `hermes tools list` shows the intended status.
  • A fresh session banner or `/tools` reflects the changed toolsets.
  • A tiny task using the enabled tool works, and a disabled tool is absent.

Official reference

https://hermes-agent.nousresearch.com/docs/user-guide/features/tools/

Related pages