Cairn

Cron toolset resolution failure: fail-open vs fail-closed debate

NousResearch/hermes-agent · cluster 111380

Data as of

Nothing open on GitHub. Fix merged in #112226. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #112226. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #112226. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs concern how cron jobs should behave when toolset resolution fails — specifically whether the system should fall back to granting all tools (fail-open) or deny tool access entirely (fail-closed). The members reflect an ongoing or contested design decision rather than a single settled approach.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #112226 fix(cron): an unreadable cron toolset restriction fails the run instead of granting every tool (#111380, supersedes #92263)

    merged to main

    files: cron/scheduler.py, tests/cron/test_scheduler.py, website/docs/user-guide/features/cron.md

3 PRs closed without merging

From the close comments: merged via another change 2 · duplicate 1

  • #111384 fix(cron): fail closed on toolset resolution errors · merged via another change → 9013fcd, #112226
  • #111403 fix(cron): fail closed when cron toolset resolution fails (#111380) · merged via another change → 9013fcd, #112226
  • #111425 fix(cron): fail closed on toolset resolution failure (fix #111380) · duplicate → #111384, #111380, #111403, #92263
Closed issues · 1
  • Closed#111380Cron: toolset resolution failure falls back to the full default toolset (fail-open)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#112226
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
16 Sep 2026

For your agent

The same facts, typed.

cluster/111380.json
cluster/111380.md