If this sounds like your week
When Windows Search gets in the way
project managers need recall across client folders without indexing the entire disk or uploading project names. Windows Search treats the PC as the boundary rather than the exact watched-folder list in Search Sentinel settings. SSD churn across unrelated archives is most visible while a meeting is running in the browser.
Where tooling usually breaks
Why local-first matters
index.db, config.json, and logs stay under %APPDATA%\SearchSentinel instead of a vendor-hosted workspace. Search queries are not uploaded for AI enhancement, analytics, or ad targeting. You buy the app once and keep the search index as a local workstation asset.
Technical proof points
- Watched folders - config.json - SQLite FTS5 - No network logger - Local-first storage - Release path redaction