Cron job silent suppression bypass controls
NousResearch/hermes-agent · cluster 53230 · cron
Data as of
5 open items. Fix attempted, not merged.
The short answer
1open issue
4open PRs
6items grouped
- Known?
- Yes. 6 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 4 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and PRs address a bug where a global [SILENT] prompt policy suppresses recurring briefing and report jobs that should always deliver output. The work involves adding per-job flags or delivery policies to allow individual cron jobs to override silent suppression.
Open issues1
- Issue#53230`[Bug]: Generic cron [SILENT] prompt policy suppresses recurring briefing/report jobs that should always send an all-clear`
Open PRs4
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#53270 fix: add per-job allow_silent flag for recurring briefing/report jobs · superseded by another PR →
#53248
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.33: 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
- Closed issues
- 0
- Attempts
- 1 PR closed without merging