# NousResearch/hermes-agent · state.db multi-writer corruption and detection fixes

## Open now

- Nothing open on GitHub.

A bug report and two fixes addressing SQLite WAL corruption caused by multiple processes simultaneously writing to state.db. Work covers detection of concurrent writers at open time and prevention of writer multiplication during startup.

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

- #100896: \[Bug\] state.db corruption x4 in 5 weeks (gateway+dashboard multi-writer WAL) — "5 live SessionDB handles" warning fires 7 min before onset; journal_mode=delete containment

## Prior & competing PRs

- **#100958: fix(state): stop concurrent startup from multiplying state.db writers**. closed without merge
  - maintainer direction: category `stale_abandoned`; implication `active`; refs `#101191`, `#100896`, `#100767`
- **#102663: fix(state): detect multi-process WAL writer set at state.db open**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `902eccae3f`, `#108076`

## Fix status

- No merged fix on record.