NousResearch/hermes-agent
Cron per-job opt-in for the send_message tool
Cluster 20138 · cron. Data as of
1 open item. Fix attempted, not merged.
The short answer
1open issue
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 2 PRs 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 0 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThe members share a theme: letting individual cron jobs opt in to messaging, specifically the send_message tool. They include a feature request, an issue titled similarly, and two pull requests with identical titles about respecting a per-job messaging opt-in; titles alone do not show their status or outcome.
Open issues1
- Issue#20140[Feature]: Cron: allow per-job opt-in to send_message tool
Open PRs0
2 PRs closed without merging
From the close comments: superseded by another PR 1 · other 1
Closed issues · 1
- Closed#20138Cron: allow per-job opt-in to send_message tool
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.39: 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
- 1
- Attempts
- 2 PRs closed without merging