memgit

Show recent checkpoint history for the memory store — when memories were last synced and what changed. CALL THIS: to understand how fresh the memory store is, or to debug sync issues.

Fetch a single memory by its exact slug identifier. CALL THIS: when search_memories returned a relevant slug and you need the full details (why, when to apply, tags). Slugs are kebab-case identifiers like 'ig-pipeline-no-fallback' or 'trading-capital-track'.

List all memories, returning slug + rule for each. CALL THIS: to browse what's stored, discover memory slugs for get_memory, or audit the full memory set. For finding relevant memories on a topic, use search_memories instead — it is faster and ranked.

Get a compact 'where we left off' digest: the status board (live entity state from tracker memories), the last checkpoints (most recent actions taken), staged work in flight, recently updated memories, critical rules that always apply, and a memory index of topics with counts. This is the authoritative record of what happened in previous sessions. Use your judgment about when the current request depends on that record: any ask that presupposes shared history — continuing work, referencing 'pending' or 'recent' things, resuming after a break — can't be answered correctly from the conversation or open files alone, however plausible they look. An open file shows what the user is looking at; this shows what was actually done last. Cheap to call, so prefer checking over assuming; skip it only when the request is clearly self-contained.

Persist a new fact, rule, preference, or lesson to the memory store for future sessions. CALL THIS: whenever you learn something the user would want you to remember next time — a preference they stated, a rule they corrected you on, a project decision, a lesson from a mistake, or a reference to an external system. Do NOT save ephemeral or task-specific details; save durable facts only. If a memory with the same slug already exists, this updates it — that is exactly how 'tr' trackers are meant to be updated when an entity's state changes. When this memory CORRECTS or replaces existing ones, pass their slugs in 'supersedes' instead of writing 'CORRECTED:' prefixes or leaving stale duplicates.

Search your persistent memory store for facts, rules, and lessons relevant to the current task. CALL THIS: at the start of every session, before answering questions about past work, before applying preferences the user may have expressed before, or whenever you are unsure whether you have prior context on a topic. SCOPED BY DEFAULT: results come from the current project's family plus global (project-less) memories — other projects' memories never appear unless you widen. To widen: pass all_projects=true to search the entire store (each hit then carries its 'project' label), or pass project=<label> to hard-filter to one specific project. The resume digest and <memgit-recall> blocks show a memory index with counts ('+N more on <topic>') — those topics are guaranteed to return results here; the injected blocks are a teaser of this store, not its full depth. Returns memories ranked by relevance — only what matters, not everything. Superseded (corrected/replaced) memories are hidden by default. This is faster and more relevant than reading individual memory files.

Promote an UNVERIFIED (candidate) memory to trusted/committed after you have confirmed its content is a legitimate fact. Once verified, it can inject into high-authority context again. Use this to resolve the candidate/committed boundary in-session (the operator does not do it manually). Pass verified=false to demote a memory back to candidate.