Nous Research Introduces ‘Blank Slate’ Mode for Hermes Agent, Enhancing Control for AI Developers

The ‘Blank Slate’ mode is designed to invert the traditional onboarding process. Instead of starting with a fully loaded default configuration, users now begin with a minimal setup. This includes only the selected provider, model, File Operations, and Terminal functionalities. All other advanced tools and capabilities are disabled by default, requiring developers to explicitly opt-in for each feature they wish to use.

A Shift Towards Granular Control

Unlike the existing ‘Quick Setup’ and ‘Full Setup’ modes, which provide comprehensive toolsets out of the box, ‘Blank Slate’ emphasizes a minimalist starting point. This means that features such as web browsing, code execution, vision, memory, delegation, cron, skills, plugins, and MCP servers are initially inactive. The core idea is to enable developers to build their agents from the ground up, integrating only the components essential for their specific tasks.

This approach offers several advantages, particularly for those developing highly specialized AI applications. By starting with a lean configuration, developers can potentially achieve more efficient performance, reduce resource consumption, and ensure more predictable agent behavior. Unnecessary components are simply not loaded, minimizing potential overhead and complexity.

Persistent Configuration Management

A key aspect of the ‘Blank Slate’ mode is its persistent configuration management. When a developer chooses this mode, the decisions regarding enabled and disabled toolsets are written directly to disk. This is managed through an explicit `platform_toolsets.cli` list and `agent.disabled_toolsets` file. This mechanism ensures that the agent’s surface remains pinned to the user’s choices.

Practical Implications for Developers

The ‘Blank Slate’ mode is particularly well-suited for developers who require precise control over their agent’s capabilities. For instance, a developer building an agent for a very specific data processing task might only need file operations and terminal access. By using ‘Blank Slate’, they can avoid loading web browsing or vision capabilities, which would be superfluous and potentially introduce security or performance overhead.

Developers can incrementally add capabilities as their project evolves. For example, after an initial setup, a developer might use `hermes tools` to re-enable a specific toolset like web access, or `hermes skills opt-in –sync` to seed skills on demand. This modularity supports iterative development and testing, ensuring that each new component integrates smoothly without unintended interactions.

System Requirements for Local Setups

Feature	Description
Default State	Starts with only provider, model, File Operations, and Terminal enabled
Customization	Users manually opt-in for features like web access, code execution, vision, memory, and delegation
Durability	Configuration is written to disk via `platform_toolsets.cli` and `agent.disabled_toolsets`
Context Window	Requires a model with at least 64,000 tokens of context for local setups