Skip to main content
cacheDir contains both rebuildable indexes and durable state. The name cache.db does not mean that deleting the file is a safe index reset. Stop all processes sharing the state directory before making a cold backup, or use a backup method that guarantees a consistent SQLite snapshot. Do not copy just a live .db file while ignoring its WAL, and do not delete database files as a shortcut for search maintenance.

Resetting the search index

Use reset_vault_cache with its confirmation flow. It is scoped to a vault and selected table families, not an entire database file. The default includes chunks, embeddings and idempotency keys; event-log and committed-capture deletion are opt-in. To preserve operational history while forcing a fresh index, explicitly set include.idempotency_keys, include.event_log and include.capture_committed to false, with include.chunks and include.embeddings set to true. Chunk deletion also clears associated chunk FTS/vector entries and may cascade to dependent derived rows. Memory entities/relations/observation history and write-provenance rows/heads are outside the tool’s reset table set. The tool does not itself perform a reindex. Follow it with index_vault or completed boot reconciliation, and verify retrieval. For a model or dimension change, follow the coordinated embedding migration procedure, including all processes and vaults that share the database. For cleanup of superseded embedding generations only, use include.chunks: false and include.embeddings: "inactive"; leaving chunks enabled would also delete their active embeddings. Choose the remaining flags explicitly according to the state you intend to retain.