NousResearch/hermes-agent

Session lease and resource leak fixes

Cluster 85431 · gateway. Data as of 2026-10-29 11:48 UTC

Nothing open on GitHub. Fix merged in #86755 on 15 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #86755. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #86755. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #86755, then check it covers your case.

Read #86755 Pick up a Lab task

These items address leaking or mismanaged active-session leases, including registry pinning at acquire time and cleanup of related resource leaks such as file descriptors, browser daemons, and scope handling. The members share a theme of session and resource lifecycle correctness.

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.

#86755 fix: purge resource-leak cluster — thread output FDs, browser daemons, pet image cache, Relay scope pop, session leases

merged to main

files: agent/pet/generate/orchestrate.py, agent/relay_llm.py, agent/relay_runtime.py, agent/thread_scoped_output.py, contributors/emails/[redacted:email], hermes_cli/active_sessions.py, hermes_cli/observability/relay_shared_metrics.py, tests/agent/test_pet_generate.py, tests/agent/test_relay_scope_pop_metadata.py, tests/agent/test_thread_scoped_output.py, tests/hermes_cli/test_active_sessions.py, tests/tools/test_browser_orphan_reaper.py, tools/browser_tool.py

1 PR closed without merging

From the close comments: done elsewhere 1

#85449 fix(gateway): pin active-session lease to its acquire-time registry (#85431) · done elsewhere → 94ce839, #85431

Closed issues · 1

Closed#85431[Bug]: Active-session leases leak when released under a multiplexed named-profile scope

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: #86755
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 15 Aug 2026

For your agent

The same facts, typed.

cluster/85431.json
cluster/85431.md