# NousResearch/hermes-agent · Recovery path when WAL guard fires

## Open now

- 1 issue, 0 PRs open on GitHub.
- #110054: Pain cluster: after the deleted-WAL guard fires there is no in-product recovery — Desktop users restart/ask-the-agent/run doctor --fix and make it worse (4 Discord threads, 13 issues this week)

A reported pain point where users have no in-product recovery after the deleted-WAL guard triggers, plus two related fixes addressing recovery flow and correct HTTP status codes in that scenario.

## TL;DR

- 3 member(s): 1 open issue(s), 0 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 #121428. Verify it addresses your case.
- **Recommended:** read PR #121428 (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.

## Open related issues

- #110054: Pain cluster: after the deleted-WAL guard fires there is no in-product recovery — Desktop users restart/ask-the-agent/run doctor --fix and make it worse (4 Discord threads, 13 issues this week)

## Prior & competing PRs

- **#121428: fix(dashboard): return 503, not 500, for a deleted WAL or replaced state.db**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/web_routers/_common.py`, `hermes_cli/web_routers/sessions.py`, `tests/hermes_cli/test_web_analytics_corrupt_store.py`
- **#110073: fix(state): in-product recovery after deleted-WAL guard fires (#110054)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `4cc4072747`, `#121428`, `#110054`

## Fix status

- Merged to main in PR #121428 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-24`.
- Subsystem: `apps/desktop`