[Bug]: Blank Slate Installation doesn't load the tools even after enabling

[sashlabs-cyber]

Bug Description

When hermes is installed with blank slate setup none of the tools other than cronjob are being loaded even after the tools are enabled in the hermes setup tools.

Debug report uploaded:
Report https://paste.rs/B7Eye
agent.log https://paste.rs/gWkmy

Steps to Reproduce

1. Fresh installation of Hermes
2. Use Blank slate for the setup
3. Ask the agent to create any files

Expected Behavior

It should create files and access the terminal tool

Actual Behavior

The agent errors out stating it only has cronjob tool and tries to create the cronjob instead.

Affected Component

Tools (terminal, file ops, web, code execution, etc.)

Messaging Platform (if gateway-related)

N/A (CLI only)

Debug Report

Report     https://paste.rs/B7Eye
agent.log  https://paste.rs/gWkmy

Operating System

Debian 13.4

Python Version

Python 3.13.5

Hermes Version

v0.18.0 (2026.7.1)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR

[alt-glitch]

This was generated by AI during triage.

Related: #49995 / #54334 (Blank Slate agent.disabled_toolsets reconcile) and #51586 (Blank Slate prompt-size / _compute_tool_definitions erasing the minimal tool surface).

Note for triage: the _save_platform_tools reconcile fix (#54334) landed before the v0.18.0 (2026.7.1) release you're running, so the desktop Toolsets-UI toggle path is already patched. Since you still see only the cronjob tool after enabling via hermes setup tools, this looks like a distinct remaining gap in the CLI tools_command -> _save_platform_tools path or in model_tools._compute_tool_definitions (posture-subtraction removing enabled toolsets that are still listed in agent.disabled_toolsets). Marked needs-repro.

Workaround: edit config.yaml and remove the enabled toolsets from agent.disabled_toolsets directly.

[sashlabs-cyber]

@alt-glitch Tools are not present in the agent.disabled_toolsets in the config.yaml. still the tools are not being loaded into the agent.

[bbopen]

Root cause found (reproducible on a clean checkout, not config corruption):

In model_tools._compute_tool_definitions, the disabled_toolsets subtraction loop preserves shared core tools only for hermes-* platform bundles (the #33924 fix — it subtracts just bundle_non_core_tools()); every other name takes the else branch and gets a full resolve_toolset() subtraction. coding is a posture toolset (posture: True) whose definition re-lists _HERMES_CORE_TOOLS (terminal, read_file, write_file, web_search, execute_code, browser_*, skills, …) that it does not own — so disabled_toolsets: [coding] strips all of those from the whole schema, leaving only the handful nothing in coding re-lists (computer_use/text_to_speech/project_*).

Repro (no config needed):

from model_tools import get_tool_definitions
len(get_tool_definitions(quiet_mode=True))                                 # 34
len(get_tool_definitions(disabled_toolsets=["coding"], quiet_mode=True))   # collapses; terminal/web_search/write_file gone

Atomic disables behave correctly and must keep doing so: ["terminal"] removes terminal, ["file"] removes write_file.

The minimal fix is to extend the #33924 core-preserving branch to also match posture toolsets (startswith("hermes-") or get_toolset(name).get("posture")) and subtract bundle_non_core_tools() for them. coding is the only posture: True toolset, so atomic toolsets stay fully removable; a blanket core-preservation would be wrong since many toolsets legitimately contain core tools.

Note on #57332: it stops hermes setup writing coding into disabled_toolsets on new blank-slate installs, but doesn't help existing configs that already contain the entry and doesn't change the subtraction, so the collapse stays reachable. Complementary.

Opened a draft fix + regression test as #57546.