# NousResearch/hermes-agent · Exclude cron sessions from trigram FTS index

## Open now

- Nothing open on GitHub.

These items all concern a performance optimization to prevent cron-sourced sessions from being included in the trigram full-text search index. The goal is to avoid unnecessary index inflation caused by cron runs.

## 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 #101725. Verify it addresses your case.
- **Recommended:** read PR #101725 (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.

## Closed / duplicate issues

- #101199: perf(state): exclude cron-source sessions from trigram FTS index (messages_fts_trigram_src)

## Prior & competing PRs

- **#101725: perf(state): exclude cron sessions from the trigram FTS index (salvage #101266)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_state_common.py`, `hermes_state_schema.py`, `hermes_state_search.py`, `tests/state/test_fts_trigram_cron_exclusion.py`
- **#101266: perf(state): keep cron runs from inflating the trigram index**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `593aa74c61`, `#101725`

## Fix status

- Merged to main in PR #101725 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-02`.