← All Docs

Changelog

Release notes for Lore CLI and public documentation.

0.13.0 - April 30, 2026

This release simplifies the repo-local context vocabulary around add and remove.

  • lore context add <project> is now the command for creating and registering a repo-local .lore/ working copy.
  • lore context remove removes that generated working copy and unregisters daemon refresh.
  • Empty projects are allowed: context add creates the scaffold now, and daemon refresh populates it after sources for that project exist.
  • A repo-local .lore/ working copy currently tracks one Lore project. Adding another project replaces clean context, while active proposals require review or explicit --force.
  • Docs now describe future multi-context workspaces for product, marketing, business, compliance, or other permissioned Lore contexts without changing the v1 workflow.

0.12.0 - April 30, 2026

This release makes Lore easier to use from code repos and safer to keep running in the background.

Project Context Working Copies

  • Repo-local .lore/ working copies can register the current repo for daemon-managed context refresh.
  • Working copies include all non-deleted project sources by default. Use --limit <n> only for deliberately smaller task packs.
  • .lore/ working copies use copied snapshots, not symlinks.
  • Clean snapshots auto-refresh after daemon sync cycles.
  • Local edits in .lore/sources/ remain proposed corrections and are never approved automatically.
  • lore context list shows repos with Lore context and their last refresh result.
  • lore context remove removes only the generated .lore/ folder.

Correction Review

  • Correction diffs and status output are colorized and more Git-like.
  • Short correction IDs are accepted where unambiguous.
  • Browse defaults to recently edited documents, making approved corrections easier to find.
  • Approval, rejection, reconciliation, and direct Browse edits now use stricter revision checks and rollback paths.

Sync And Repair

  • Lore Cloud/Supabase is the primary sync layer. Git in LORE_DATA_DIR is optional local history.
  • lore sync repair rebuilds generated data-repo caches, imports deletion identities into Supabase, and untracks cache files that should not participate in Git merges.
  • The daemon detects broken data-repo Git state quickly, reports lore sync repair, and still refreshes project .lore/ working copies where safe.
  • Deleted source identities now live in Supabase; local deleted-hashes.json is a rebuildable cache/fallback.

Developer And Agent Docs

  • Added generated Supabase database types in the CLI repo and a db:types script for future migrations.
  • Updated bundled agent skills so Claude Code, Gemini, Codex, OpenClaw, and generic MCP agents understand repo-local .lore/ working copies.
  • Updated the website docs, CLI docs, project context docs, FAQ, and llms.txt output for the new operating model.