Skip to Content
remimem

Files and environment

What remimem writes where, what to commit, and the environment variables it reads.

In the project

config.json
memory.json
index.db
index.db-wal
index.db-shm
.gitignore
FileWhat it isCommit it?
.remimem/config.jsonYour settings. Created empty by init.Yes, to share settings
.remimem/memory.jsonProject memory, one memory per line. The source of truth for memories.Yes, to share memories
.remimem/index.dbThe index: chunks, keyword index, vectors, call graph, query log. One SQLite file.No. init adds it to .gitignore.
.remimem/index.db-wal, -shmSQLite's write-ahead log, present while the index is openNo (covered by the same .gitignore line)

Deleting .remimem/index.db is always safe: the next remimem index rebuilds it, and memories come back from memory.json.

In your home folder

PathWhat it is
~/.cache/remimem/modelsDownloaded embedding models. The default model is 23 MB.
~/.cache/remimem/benchBenchmark clones and their indexes, only if you ran remimem bench

Both move with REMIMEM_CACHE_DIR. Deleting them is safe; models download again on next use.

Environment variables

VariableDefaultMeaning
REMIMEM_LOG_LEVELwarnerror, warn, info, or debug. Logs go to stderr only. debug adds timings for each indexing stage and each tool call.
REMIMEM_CACHE_DIR~/.cache/remimemWhere models and benchmark data are kept
OPENAI_API_KEYnoneRequired with "provider": "openai"
VOYAGE_API_KEYnoneRequired with "provider": "voyage"

Index format and upgrades

The index has numbered migrations, applied automatically when a newer remimem opens an older index. When an upgrade changes what the parser or chunker stores, the next index run rebuilds every file on its own. An older remimem refuses to open an index written by a newer one:

The index was written by a newer remimem (schema N); upgrade remimem or delete .remimem/index.db and run `remimem index`

On this page