Cairn
NousResearch/hermes-agent

Desktop profile retry storm and stale scheduler fixes

Cluster 111338. Data as of

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

These items address unbounded retry behavior when profiles exceed backend slots causing session-area flicker, and a cron scheduler that does not reflect live profile additions or deletions. The group covers the bug report and related fix attempts.

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.

  • #112251 fix(desktop): session area stops flickering when profiles outnumber backend slots; cron ticker follows profile create/delete live (#111338, salvage #111352)

    merged to main

    files: apps/desktop/electron/main.ts, apps/desktop/electron/pool-spawn-coordinator.test.ts, apps/desktop/electron/pool-spawn-coordinator.ts, hermes_cli/web_server.py, tests/cron/test_cron_multiplex_desktop_ticker_scope.py, tests/hermes_cli/test_desktop_cron_ticker_profiles.py, website/docs/user-guide/multi-profile-gateways.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #111352 fix(desktop): bound background profile hydration retries · merged via another change → aa03d38, #112251
Closed issues · 1
  • Closed#111338[Bug]: Desktop session-area flicker — unbounded slot-retry storm when profiles > maxBackends, and stale cron-scheduler profile list after profile delete
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
#112251
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
16 Sep 2026

For your agent

The same facts, typed.

cluster/111338.json
cluster/111338.md