lore captures
See your org’s session-capture policy and what was captured from you. See Session capture.
Usage
lore captures policy [--org <org>]
lore captures ls [--org <org>] [flags]
lore captures show <id> [--org <org>]Flags for ls
| Flag | Description |
|---|---|
--session <id> | Only batches containing this session |
--harness <id> | Only this harness |
--project <key> | Only this project |
--since <YYYY-MM-DD> / --until <YYYY-MM-DD> | Received within these dates |
--person <email> | A member’s captures (org owner only) |
--page <n> | Page of results, 0-indexed |
Without --org, lore uses your only org, or asks you to pick one. policy prints the responsibility statement in your locale (LANG); org redaction rules are shown to the org owner, and only counted for everyone else.
When your org distills captures, ls also shows each delta’s distillation state as known on this machine (distillation runs where the capture was made): queued, distilled (n record(s)), distillation skipped:<reason>, distillation over-budget or distillation failed. See From captures to org memory.