NousResearch/hermes-agent

MCP/TUI startup memory reduction efforts

Cluster 53415 · dashboard. Data as of

Nothing open on GitHub. Fix merged in #77511 on 3 Aug 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 #77511. 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.

A cluster of issues and pull requests focused on diagnosing and reducing high resident memory usage at startup, particularly from MCP server initialization and related allocator behavior. Approaches include lazy startup, schema caching, allocator trimming, and telemetry.

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.

  • #76905 feat(mem): config-driven allocator trim with telemetry (#66355 salvage)

    merged to main

    files: gateway/run.py, hermes_cli/config_defaults.py, hermes_cli/mem_trim.py, run_agent.py, tests/gateway/test_memory_trim_housekeeping.py, tests/hermes_cli/test_mem_trim.py, tests/test_tui_gateway_server.py, tui_gateway/server.py, tui_gateway/slash_worker.py

  • #77511 perf(mcp): lazy server startup from fingerprint-keyed schema cache (#56832 extract-salvage)

    merged to main

    files: tests/tools/test_mcp_lazy_start.py, tests/tools/test_mcp_schema_cache.py, tools/mcp_schema_cache.py, tools/mcp_tool.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #56832 perf(dashboard): reduce idle memory from MCP startup · superseded by another PR → #76905, #77511
Closed issues · 1
  • Closed#53415Desktop TUI Gateway Python process resident memory ~1GB on startup (state.db 469MB + pymalloc)
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

Subsystem
dashboard
Merged PRs
#76905, #77511
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
3 Aug 2026

For your agent

The same facts, typed.