NousResearch/hermes-agent

Cron profile isolation and status accuracy fixes

Cluster 98790. Data as of

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

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #99375. 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.

These items address a bug where cron status reporting and job delivery were not properly isolated per profile, potentially showing or using another profile's gateway. The work involves fixes to profile-level filtering, heartbeat guards, and status output to ensure each profile's cron jobs operate independently.

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.

  • #99375 fix(cron): profile jobs deliver via their own bot and cron status stops lying (#94862 #99028 #98790, salvage x6)

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], cron/scheduler.py, cron/scheduler_provider.py, gateway/run.py, hermes_cli/cron.py, hermes_cli/gateway.py, tests/cron/test_87033_cronjob_gateway_liveness.py, tests/cron/test_cron_home_target_profile_scope.py, tests/cron/test_cron_multiplex_profile_route_preflight.py, tests/cron/test_run_one_job.py, tests/cron/test_scheduler_provider.py, tests/cron/test_sessiondb_init_hang.py, tests/hermes_cli/test_cron_status_profile_isolation.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #98803 fix(cron): profile isolation — systemd filter + heartbeat guard · merged via another change → 9eb832a, #99375, #98790
Closed issues · 1
  • Closed#98790Bug: `cron status` reports another profile's gateway as proof that THIS profile's jobs will fire
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

Merged PRs
#99375
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.