NousResearch/hermes-agent

Cron profile-scoped job and script path handling

Cluster 40801 · cron. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 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
1 issue and 0 PRs.

These items concern how cron jobs interact with per-profile versus default-profile storage and script directories, including reversals of earlier changes and fixes to path-guard logic for profile-scoped jobs.

Open issues1

  • Issue#40801Cron script-path guard rejects profile-scoped jobs referencing default-profile scripts directory (inverse of #32091)

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #40918 fix(cron): allow profile-scoped jobs to reference default-profile scripts · other → #40801, #43956, #28124
  • #55070 fix(cron): allow profile-scoped jobs to run scripts from the default-profile scripts dir (#40801) · duplicate → #40801, #40918, #41008, #54288, #34243
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.67: 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

Subsystem
cron
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.