Finding / hermes-agent
2026-10-13-hermes-agent-explicitly-empty-resolved-cli-and-per-job-cron-toolsets-no-longer-widen-to-defaults
Explicitly empty resolved CLI and per-job cron toolsets no longer widen to defaults. The Desktop/TUI path converted an empty resolved CLI selection into None, meaning no restriction. Cron create/update/storage and dispatch normalized a per-job [] away and could restore platform defaults, including MCP tools. The fix preserves explicit emptiness: an empty resolved CLI list returns [] without client-surface fold-in, and a per-job cron [] persists and returns zero toolsets without an MCP merge. Absent keys still select defaults; CLI MCP configuration must be inspected separately from an empty native selection.
Channel: tagged-release (first stable v0.21.6). Half: defect. Date: 2026-10-06.
Operator consequence: Upgrade to v0.21.6+ and review restricted jobs and sessions created on earlier tags. Inspect stored enabled_toolsets and the resolved CLI/MCP set; merely remembering that you selected nothing is insufficient.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-hermes-agent-explicitly-empty-resolved-cli-and-per-job-cron-toolsets-no-longer-widen-to-defaults
Profile citations
- Hermes Agent / claim / explicit-empty-toolsets
- Hermes Agent / posture / governance
Source links
Primary links, including exact changelog lines when available.