index
--rebuild wipes extracted entities and their edges (mentions and relationships found in
your content), then re-extracts from scratch. It does not touch memories, conflicts, or the
replaces/distinct edges created by resolving conflicts.
reembed
~/.memloom/config.env, then stamp the store with the new fingerprint. Run this after
switching providers or models, for example after adding OPENROUTER_API_KEY to leave
offline mode: without it the daemon refuses to start, because old and new vectors live in
incompatible spaces.
Interrupting is safe: memories and files are never touched, only their vectors, and running
the command again resumes where it stopped. Costs one embedding API call per 64 items.
--force re-embeds even when the store already matches the configured provider and nothing
is missing.
A typical offline-to-cloud migration:
auto-index
MEMLOOM_AUTO_INDEX in config.env is only the default
before the first use of this switch. Needs an API key; offline mode cannot enable it.
schema
The vocabulary itself, and how the LLM proposes new entries for your approval, is covered in
The graph.