Cairn

Desktop launch crash from log buffer init order

NousResearch/hermes-agent · cluster 101941

Data as of

Nothing open on GitHub. Fix merged in #102001. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #102001. 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 issues and fixes address a desktop app crash on launch caused by code attempting to push to a log buffer (rememberLog/hermesLog) before it was initialized, due to module evaluation order. Multiple fixes approach the same initialization sequencing problem.

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.

  • #102001 fix(desktop): packaged app no longer crashes on launch with undefined.push in rememberLog (#101941, salvage #101945)

    merged to main

    files: apps/desktop/electron/main.ts

4 PRs closed without merging

From the close comments: merged via another change 4

  • #101945 fix(desktop): declare rememberLog state before the top-level pool-limits read · merged via another change → 05f548f, #102001
  • #101964 fix(desktop): initialize hermesLog before pool limits · merged via another change → 05f548f, #102001, #101945
  • #101967 fix(desktop): read pool limits after the log buffer exists · merged via another change → 05f548f, #102001, #101945
  • #102017 fix(desktop): declare rememberLog state before module-eval callers, with a regression guard · merged via another change → 05f548f, #102001, #101945
Closed issues · 1
  • Closed#101941[Bug]: Desktop main process crash on launch — rememberLog push on undefined hermesLog (pool-limits init order)
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.33: 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
#102001
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
3 Sep 2026

For your agent

The same facts, typed.

cluster/101941.json
cluster/101941.md