lorelisted

# lore — curated memory + session recall CLI (always via Bash): `python3 "${CLAUDE_PLUGIN_ROOT}/bin/lore.py" <cmd>` — aliased below as `lore`. The current memory snapshot was injected at session start. A write reaches the files at once but reaches your context only at the next injection — next session by default, or within `LORE_REFRESH_SECS` when the mid-session refresh is on; the snapshot's own last rule says which applies. Either way `lore memory show` reads the files live. State lives in `~/.claude/lore/` (override: `LORE_ROOT`). ## Writing memory ```sh lore memory add --scope user "prefers MRs without squash; reviews in caveman mode" lore memory add --scope project "task test starts throwaway Postgres; bare pytest fails DB tests" lore memory replace --scope project --match "throwaway Postgres" "merged, denser fact" lore memory remove --scope user --match "substring" lore memory show ``` - **user scope** (cap 1375 chars): who the user is, preferences, communication style. Global. - **project scope** (cap 2200 chars): this repo's environment facts, conventions, workarounds, corrections. Keyed by cwd. - Store a fact **the moment you learn it** — a correction from the user, a discovered footgun, a preference. One line, dense, declarative, no prose. - Caps are hard. An over-cap write fails and lists all entries — consolidate overlapping entries with `replace` (merge several facts into one dense line), then retry. Consolidate proactively past 80% usage. - Do NOT store: ta