# NousResearch/hermes-agent · SessionDB file descriptor leak in react_to_message

## Open now

- Nothing open on GitHub.

These issues and PRs address a file descriptor leak caused by react_to_message not closing its dedicated SessionDB after each call. Work also covers hardening SessionDB handling, vision routing, and test isolation.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #83072: react_to_message leaks its dedicated SessionDB on every call

## Prior & competing PRs

- **#83079: fix: harden SessionDB, vision routing, and test isolation**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#83072`, `#83226`, `#83097`, `#92167`, `#83089`, `#92168`, `#83095`, `#92169`
- **#83885: fix(desktop): close SessionDB in react_to_message tool to stop FD leak**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#83079`

## Fix status

- No merged fix on record.
- Subsystem: `agent`
