Skip to Content
V1CLI Referencelore memory

lore memory

Manage your org’s memory. See Reading org memory.

lore memory reclassify

Backfill the category and project of the org’s memory records that have none, typically records stored before categories existed. Only the org owner can run it.

lore memory reclassify [--org <org>] [--dry-run] [--harness <id>]
FlagDescription
--dry-runReport the proposals without writing anything
--harness <id>Harness to classify with (default: the org’s distillation harness: claude or codex)

How it decides.

  • Project comes first from the record’s capture provenance, when the capture is still retained. Otherwise it comes from the record’s first tag, when that tag names exactly one known project. Only then does it come from the model, which may only choose a project the org already knows; it never makes one up.
  • Category comes from the org’s distillation harness (Claude Code or Codex), run headless on your machine exactly like distillation: isolated, signed in as it always is, with no API key. Records are sent 20 at a time. An answer outside the four categories leaves the record uncategorized.

The command only changes category and project. Author, platform, content, tags and the last-updated date stay as they were, so the Overview’s “updated this week” isn’t inflated by the backfill.

Run it in three steps.

lore memory reclassify --org <org> --dry-run # review the report lore memory reclassify --org <org> # write it lore memory reclassify --org <org> --dry-run # only intentionally unclassified records remain

The report lists each record with its proposed category and project, where each value came from (provenance, tag or model), and the input characters sent to the harness. Records that already have both fields are skipped, so running the command again changes nothing it already classified.

© 2025 Lore · Built by M1 Cloud