NousResearch/hermes-agent

Cron profile-scoped vs shared gateway visibility issues

Cluster 99631. Data as of

Nothing open on GitHub. Fix merged in #126156 on 28 Sep 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 #126156. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #126156. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern how cron job listing and execution behave when profile-scoped homes interact with a shared gateway, including false 'gateway not running' warnings and ensuring job-related behaviors follow the owning profile under multiplexed setups.

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.

  • #126156 cron under multiplex: liveness, manual-run delivery, managed routes, degraded-send retention and worker secrets follow the job's owning profile (#121881 #99579 #99631 #124248 #120330 #125363 #121212 #121929)

    merged to main

    files: contributors/emails/[redacted:email], cron/jobs.py, cron/scheduler.py, cron/scheduler_delivery.py, cron/scheduler_preflight.py, hermes_cli/cron.py, tests/cron/test_cron_reconnect_only_rejection.py, tests/cron/test_external_worker_secret_sources.py, tests/cron/test_preflight_managed_routes.py, tests/hermes_cli/test_cron.py, tests/hermes_cli/test_cron_satellite_diagnostics.py, tests/tools/test_cronjob_run_immediate.py, tests/tools/test_cronjob_run_primary_routed.py, tools/cronjob_tools.py

1 PR closed without merging

From the close comments: done elsewhere 1

  • #99659 fix(cron): see the shared gateway from a profile-scoped cron list · done elsewhere → #126156
Closed issues · 1
  • Closed#99631cron list warns 'Gateway is not running' on profile-scoped homes even when the shared gateway is firing jobs
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
#126156
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
28 Sep 2026

For your agent

The same facts, typed.