Cairn
NousResearch/hermes-agent

Gateway thread and file descriptor growth reclamation

Cluster 128969 · agent. Data as of

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

These members all concern the gateway accumulating threads (and, in one case, file descriptors) over time, including memory-provider threads tied to agent-cache churn and lingering daemon or background workers. They describe proposed or discussed reclamation of these resources at runtime; the titles alone do not show whether any change was completed or is effective.

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.

  • #137156 Gateway: stop memory-provider threads and fds from growing with agent-cache churn (salvage #126359, #131357)

    merged to main

    files: acp_adapter/commands.py, acp_adapter/server.py, agent/agent_init.py, agent/memory_manager.py, agent/memory_manager_tools.py, agent/system_prompt.py, gateway/run_shutdown.py, run_agent.py, tests/agent/test_builtin_memory_disabled_surface.py, tests/agent/test_memory_provider.py, tests/agent/test_memory_stalled_background_call.py, tests/gateway/test_agent_cache_memory_lifecycle.py, tools/mcp_tool_agent.py

1 PR closed without merging

From the close comments: other 1

  • #130979 perf(gateway): reclaim completed background threads and lingering workers (#128969) · other
Closed issues · 1
  • Closed#128969perf(gateway): daemon threads accumulate without runtime reclamation — only restart clears them
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
agent
Merged PRs
#137156
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
19 Oct 2026

For your agent

The same facts, typed.

cluster/128969.json
cluster/128969.md