reindex

Usage

machine-memory reindex --remote
machine-memory reindex --remote --json-min
machine-memory reindex --remote --quiet

reindex queues all retained memory IDs for the current repository, including deletion tombstones. The API’s vector coordinator reads current D1 rows, embeds active memories, and removes inactive or deleted memories from Vectorize. Run it after remote provisioning, after migrating to a new embedding index, or when vectors need to be repaired.

New and updated memories synchronize automatically, so reindexing is normally a backfill or recovery operation rather than part of every write.

The command requires --remote; local databases do not have a Vectorize binding.

Success means the work is durably queued, not that semantic search already reflects it. The coordinator retries failed delivery with exponential backoff and periodically repairs delivered entries. Re-running the command is safe; it never indexes a client-side snapshot.

Output

1. Use --json-min to get a stable machine-readable object:

{
  "repository": "owner/repository",
  "queued": 24,
  "indexing": "queued"
}

2. Use --quiet when no success output is desired. Non-TTY output does not emit terminal control sequences.