# NousResearch/hermes-agent · state.db journal mode warnings and configuration fixes

## Open now

- Nothing open on GitHub.

These items address silent or problematic handling of SQLite journal_mode settings in state.db, including a corruption scenario where journal_mode reverted to WAL unexpectedly. Changes add warnings and improve configurability around journal mode behavior.

## 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 #96439. Verify it addresses your case.
- **Recommended:** read PR #96439 (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: `resolved` · deciding PR(s): `pr-96439`. 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

- #89293: Repeated state.db corruption on busy single-host deployment (3 incidents in 8 days): lock storm + restart-in-window + journal_mode silently reverted to WAL after upgrade

## Prior & competing PRs

- **#96439: state.db journal-mode choices are no longer silently ignored; synchronous is pinnable everywhere (salvage #85609, #89393, #90892)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `cli-config.yaml.example`, `hermes_state.py`, `tests/test_journal_mode_config.py`, `tests/test_journal_mode_upgrade_warning.py`, `tests/test_state_synchronous_pragma.py`, `website/docs/user-guide/configuration.md`
- **#89393: fix(state): warn when an existing database's journal_mode is flipped to WAL**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#96439`, `#85609`, `#89293`, `#90950`

## Fix status

- Merged to main in PR #96439 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-27`.
- Subsystem: `agent`