# NousResearch/hermes-agent · Configurable SQLite journal_mode from config.yaml

## Open now

- Nothing open on GitHub.

These issues and PRs concern making SQLite journal settings (journal_mode, journal_size_limit, wal_autocheckpoint) configurable via config.yaml, with related concerns about WAL-mode problems on macOS virtiofs and the need to centralize database connection setup.

## TL;DR

- 7 member(s): 0 open issue(s), 3 closed issue(s), 0 open PR(s), 1 merged PR(s), 3 PR(s) closed without merging.
- A fix was merged to main in PR #74485. Verify it addresses your case.
- **Recommended:** read PR #74485 (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: `partially_resolved` · deciding PR(s): `pr-74485`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.27`: 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

- #21807: database.journal_size_limit and wal_autocheckpoint from config.yaml are never applied to SQLite connections
- #57820: feat(config): respect database.journal_mode from config.yaml — allow users to opt into DELETE mode on macOS/Linux
- #68545: state.db corruption on macOS virtiofs: checkpoint_fullfsync no-ops in Linux containers; request a configurable, centralized journal_mode

## Prior & competing PRs

- **#74485: fix(state): configurable journal_mode + WAL-refusal detection cluster (salvages #68912, #57918, #46865, #55322)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`; implication `superseded`
  - files: `cli-config.yaml.example`, `contributors/emails/[redacted:email]`, `hermes_cli/config_defaults.py`, `hermes_cli/kanban_db.py`, `hermes_state.py`, `tests/hermes_cli/test_kanban_db.py`, `tests/test_hermes_state.py`, `tests/test_hermes_state_wal_fallback.py`, `tests/test_journal_mode_config.py`
- **#57918: fix(config): respect database.journal_mode from config.yaml**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#74485`
- **#59768: feat(config): respect database journal settings for state.db (#57820)**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#57918`, `#57820`, `#21807`, `#57918`, `#57820`, `#21807`
- **#68912: fix(state): configurable journal_mode + centralize all DB openers**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#74485`

## Fix status

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