Cairn
NousResearch/hermes-agent

FTS5 index errors wrongly treated as fatal corruption

Cluster 97794. Data as of

Nothing open on GitHub. Fix merged in #108130 on 11 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #108130. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #108130. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes address a bug where errors in the FTS5 full-text search index layer of state.db incorrectly trigger fail-close behavior on turns, causing dropped messages and unnecessary destructive recovery advice. The proposed fix changes the system to fail open on FTS-index-only errors while reserving stricter handling for genuine structural corruption.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #108130 state.db FTS damage no longer kills turns; doctor/repair/recover handle real incident shapes (#97794, #88587, #100227, #103840, #106667, #102240, #98050, #103647, #96591, #105887; salvage #97843 #88604 #56824 #91413 #102808 #103657 #106890 #103321)

    merged to main

    files: agent/turn_explainers.py, contributors/emails/[email protected], contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], gateway/run_notifications.py, hermes_cli/console_engine.py, hermes_cli/doctor_state.py, hermes_cli/session_lost_and_found.py, hermes_cli/session_recovery.py, hermes_cli/sessions_cmd.py, hermes_cli/web_routers/_common.py, hermes_cli/web_routers/analytics.py, hermes_cli/web_server_sessions.py, hermes_constants.py, hermes_state_errors.py, hermes_state_fts.py, hermes_state_repair.py, hermes_state_schema.py, hermes_state_search.py (+12 more)

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #97841 fix(state): don't fail-close turns on FTS-index-only errors · done elsewhere → 04dd80a, #108130, #97843
  • #97843 fix(state): fail open on FTS5-index-only corruption instead of killing turns · merged via another change → 04dd80a, #108130, #97841
Closed issues · 1
  • Closed#97794[Bug]: Healthy state.db fail-closes turns as 'structural corruption' when only the FTS5 index layer errors (false alarm, dropped messages, destructive recovery advice)
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#108130
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
11 Sep 2026

For your agent

The same facts, typed.

cluster/97794.json
cluster/97794.md