NousResearch/hermes-agent

Cron ticker profile isolation and multiplexing fixes

Cluster 100489. Data as of

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

These items address bugs in the cron ticker where secondary profiles were not properly isolated, causing jobs to run under the wrong profile or bot. Fixes span profile scope retention across threads, gateway skipping, and fail-closed satellite delivery.

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.

  • #101245 fix(cron): multiplex ticks isolate per profile, fire the bound port, deliver satellites fail-closed (#74878 #100489 #101113 #86519, salvage #70747 #84755 #96944)

    merged to main

    files: cron/notepad.py, cron/scheduler.py, cron/scheduler_provider.py, cron/suggestions.py, hermes_cli/web_server.py, tests/cron/test_cron_multiplex_desktop_ticker_scope.py, tests/cron/test_cron_multiplex_shared_route_delivery.py, tests/cron/test_notepad.py, tests/cron/test_scheduler_provider.py, tests/cron/test_suggestions.py, tests/hermes_cli/test_cron_fire_dashboard.py, website/docs/user-guide/multi-profile-gateways.md

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #100509 fix(cron): skip running secondary gateways in desktop cron ticker (#100489) · done elsewhere → f8f4d05, #100509, #67418, #100522, #100489
  • #100522 fix(cron): keep the profile scope across the delivery worker thread · done elsewhere → 62a4599, #100489
Closed issues · 1
  • Closed#100489Desktop multiplex cron ticker delivers secondary-profile jobs with the default profile's bot
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
#101245
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.