# NousResearch/hermes-agent · SQLite busy timeout and write lock contention

## Open now

- Nothing open on GitHub.

These items address SQLite connection handling, specifically around busy_timeout configuration and reducing unnecessary write lock acquisition when opening the state database.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #108067. Verify it addresses your case.
- **Recommended:** read PR #108067 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## 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

- #101035: \[P1\] SQLite busy_timeout=0 causes SQLITE_BUSY crash loop

## Prior & competing PRs

- **#108067: Opening state.db no longer takes the write lock when nothing needs writing (#101035 #93799, salvage #106751 #101881)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_state.py`, `hermes_state_schema.py`, `tests/test_hermes_state.py`
- **#101042: fix(db): set busy_timeout=5000 on writer and reader connections**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `ff59fcd710`, `#108067`

## Fix status

- Merged to main in PR #108067 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-11`.
