How-To Series · 2: Daily Driver
Hermes · Toolsets Reference
Core, composite, platform, and dynamic toolset bundles. The complete map of what Hermes can do and how to configure it.
After this videoYou can pick the right toolset bundle for any scenario and configure it per-session, per-platform, or on the fly.
Toolsets are named bundles of tools that control what the agent can do. Core toolsets cover single capabilities like file, terminal, and web. Composite toolsets combine cores for scenarios like debugging and coding. Platform toolsets define complete configs for deployment targets like hermes-cli, hermes-acp, and hermes-api-server. Dynamic toolsets appear at runtime from MCP servers, plugins, and custom definitions. Configure them per-session with --toolsets, per-platform in config.yaml, or interactively with hermes tools and /tools commands.
About these resources. Every command in this video comes from the Toolsets Reference doc.
New words here · Plain English
one sentence each · full glossaryToolsetA named bundle of tools. Enable a toolset and all its tools become available to the agent.
Core toolsetA single-capability bundle like file, terminal, or web. One focused skill per toolset.
Composite toolsetA bundle that combines multiple core toolsets for a scenario, like debugging or coding.
Platform toolsetA complete tool configuration for a deployment target like hermes-cli or hermes-acp.
MCPModel Context Protocol. Each MCP server you configure generates its own dynamic toolset at runtime.
Sources · What this video distills
1 docs page · every command below traces to itCommands shown · Copy and paste
each shows the source doc it came fromhermes chat --toolsets web,file,terminalhermes chat --toolsets debugginghermes tools/tools list