Nous Research added a Blank Slate mode to Hermes Agent for tighter tool control

Nous Research appears to have shipped a smaller default setup path for Hermes Agent: a Blank Slate mode that starts with most toolsets disabled and lets the user opt in to capabilities explicitly.

This is useful builder context, not urgent breaking news. It is a safer setup pattern for people running agents with shell, file, MCP, browser, or messaging integrations, but it is not a frontier model release, a major platform launch, a pricing/API change, or a live security incident.

What changed

MarkTechPost reports that Hermes Agent now has a Blank Slate setup mode.
The reported default keeps only provider/model configuration plus File Operations and Terminal enabled.
Other capabilities are controlled through configuration keys including platform_toolsets.cli and disabled_toolsets.
The Hermes Agent docs sitemap shows the docs were updated on June 20, 2026, which lines up with the report.

Why builders should care

If you are giving an agent local tools, the safest default is not “turn everything on and hope prompts behave.” A minimal profile makes it easier to reason about what the agent can touch, then expand permissions only when a workflow needs them.

For BuildrLab readers, the practical takeaway is simple: treat tool access like production credentials. Start with a narrow tool surface, add integrations one at a time, and keep dangerous capabilities out of default profiles.

Caveats

This is based on a third-party report plus the public Hermes Agent docs being updated; I did not find a separate Nous blog/changelog post during this check.
It is probably a daily-news/context item rather than immediate breaking coverage.