Cron job per-job toolset scoping and access control
NousResearch/hermes-agent · cluster 10280 · cron
Data as of
2 open items. Fix attempted, not merged.
The short answer
2open issues
0open PRs
8items grouped
- Known?
- Yes. 8 related items grouped here, 4 issues 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
- 2 issues and 0 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and PRs concern giving cron jobs the ability to configure which toolsets are enabled on a per-job basis, including controlling access to messaging tools like Slack/Discord and honoring disabled toolsets during cron runs.
Open issues2
Open PRs0
2 PRs closed without merging
From the close comments: superseded by another PR 1 · other 1
Closed issues · 4
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.19: 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
- 4
- Attempts
- 2 PRs closed without merging