NousResearch/hermes-agent

Cron job repeat/schedule parsing bug fixes

Cluster 95706. Data as of

Nothing open on GitHub. Fix merged in #98290 on 30 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #98290. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Several fixes targeting cron job scheduling edge cases: handling 'repeat=forever', distinguishing recurring vs one-shot time formats like '30m', and a TypeError when creating cron jobs with no_agent and a script.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #98275 fix(cron): bare '30m' schedules recur as documented; 'in 30m' is the one-shot (salvage #78928)

    merged to main

    files: cron/jobs.py, tests/cron/test_claim_job_for_fire.py, tests/cron/test_jobs.py, tests/cron/test_oneshot_dispatch_failure_run_claim.py, tests/cron/test_terminal_job_rearm.py, tests/hermes_cli/test_web_server_cron_profiles.py, tests/test_timezone.py, tools/cronjob_tools.py, website/docs/user-guide/features/cron.md

  • #98290 fix(cron): repeat='forever' no longer breaks job updates (completes the string-repeat class)

    merged to main

    files: cron/jobs.py, tests/cron/test_jobs.py, tools/cronjob_tools.py

1 PR closed without merging

From the close comments: done elsewhere 1

  • #95727 fix(cron): accept repeat="forever" and reject other non-numeric strings cleanly · done elsewhere → 89b38ed, 52e5e7c, #98275, #98290, #7216
Closed issues · 1
  • Closed#95706cronjob create with no_agent=true + script fails: TypeError '<=' not supported between str and int
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.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

Merged PRs
#98275, #98290
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
30 Aug 2026

For your agent

The same facts, typed.