NousResearch/hermes-agent

Desktop memory growth from unbounded session data

Cluster 77311 · apps/desktop. Data as of

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

A fleet-wide issue where renderer memory grows without limit during long sessions, with related fixes targeting transcript history and agent avatar caching as contributing sources of unbounded retention.

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.

  • #118014 fix(desktop): release paged-through transcript history from the session store (#77311)

    merged to main

    files: apps/desktop/src/app/chat/index.tsx, apps/desktop/src/app/chat/transcript-retention.test.ts, apps/desktop/src/app/chat/transcript-retention.ts, apps/desktop/src/app/chat/use-transcript-retention.test.tsx, apps/desktop/src/app/chat/use-transcript-retention.ts, apps/desktop/src/app/session/hooks/use-session-actions/utils.ts, apps/desktop/src/lib/chat-messages.test.ts, apps/desktop/src/lib/chat-messages/hydration.ts, apps/desktop/src/lib/chat-messages/tool-parts.ts, apps/desktop/src/lib/chat-messages/types.ts, apps/desktop/src/store/transcript-tail.test.ts, apps/desktop/src/store/transcript-tail.ts

1 PR closed without merging

From the close comments: done elsewhere 1

  • #102064 fix(desktop): the agent avatar cache is bounded, so a long session cannot pin image bytes (#77311) · done elsewhere → f4e085e, 0142e64, #77311
Closed issues · 1
  • Closed#77311Desktop: renderer memory grows unboundedly with session content — 5 GB fleet footprint after heavy use
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

Subsystem
apps/desktop
Merged PRs
#118014
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
21 Sep 2026

For your agent

The same facts, typed.