NousResearch/hermes-agent

macOS memory trimming and session memory release in hermes serve

Cluster 131766 · gateway. Data as of

1 open item. Fix merged in #137087 on 20 Oct 2026. Check it covers your case.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
A fix was merged to main in PR #137087. 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
1 issue and 0 PRs.

The three members all concern memory growth in hermes serve/gateway, centered on mem_trim's trim_memory() reportedly doing nothing on macOS and on releasing memory from closed sessions (token memo, replay ring, gc). They appear to include an issue report, a perf change, and a fix proposal; their status and outcomes are not stated in the titles.

Open issues1

  • Issue#131766mem_trim: trim_memory() is a no-op on macOS - serve/gateway heap grows unbounded (no gc.collect / no page release)

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #137087 perf: hermes serve releases a closed session's memory (token memo, replay ring, gc on macOS)

    merged to main

    files: agent/compression_facade.py, agent/context_compressor_telemetry.py, agent/model_metadata_token_memo.py, hermes_cli/mem_trim.py, run_agent.py, tests/agent/test_token_memo_release_on_close.py, tests/hermes_cli/test_mem_trim.py, tests/tui_gateway/test_tui_gateway_event_replay.py, tui_gateway/event_replay.py, tui_gateway/session_lifecycle.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #131826 fix(mem_trim): collect on every platform and add darwin pressure relief · merged via another change → #131766, #137087
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
gateway
Merged PRs
#137087
Closed issues
0
Attempts
1 PR closed without merging
Fix link checked
20 Oct 2026

For your agent

The same facts, typed.