NousResearch/hermes-agent
cron context_from continuity and stub handling fixes
Cluster 104541 · cron. Data as of
1 open item. Fix merged in #104877 on 7 Sep 2026. Check it covers your case.
The short answer
0open issues
1open PR
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #104877. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104877. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items address how cron monitors handle no_change and silent-run stubs when context_from output selection is involved, with a focus on preserving continuity and avoiding incorrect short-circuit behavior.
Open issues0
Open PRs1
- PR#104551fix: skip no_change/silent run docs when selecting context_from output
Fixes on record
-
#104877 fix(cron): silent ticks no longer erase continuity (#104541)
files:
cron/scheduler_prompt.py,tests/cron/test_continuity_silent_audits.py,website/docs/user-guide/features/cron.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#104546 fix(cron): skip short-circuit status stubs when selecting context_from output (#104541) · done elsewhere →
e3710c1,#104541
Closed issues · 1
- Closed#104541cron: monitor no_change stubs destroy context_from/continuity
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- cron
- Merged PRs
- #104877
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 7 Sep 2026