elderfo/mehmory
Memory abstraction layer for Claude Code and Codex CLI: deterministic capture hooks plus model-driven skills over a markdown wiki in ~/.mehmory.
Merge captured mehmory inbox entries into the wiki pages under ~/.mehmory — editing pages, links, index lines and frontmatter, then clearing the inbox transactionally and committing. Use when the SessionStart nudge says the inbox is over threshold, or whenever the user asks to integrate, process, or file memory. Writes to ~/.mehmory (outside the project), so Claude Code may prompt for permission; if writes are denied nothing is lost — entries stay in the inbox for the next pass.
Full-sweep health check of the mehmory wiki under ~/.mehmory — staleness, orphan pages, contradictions across pages, and archive candidates. Reports everything first and applies only the fixes the user approves. Use when the user asks to lint, audit, clean up, or check memory. Writes to ~/.mehmory (outside the project), so Claude Code may prompt for permission on the apply step; the report itself is read-only.
Seed mehmory for the current project from scratch — survey the repo (README, package manifest, git log, docs), then write project.md, a first set of pages and the index under ~/.mehmory, and commit. Use on a fresh store, when SessionStart says the store was just created, or when the user asks to onboard, bootstrap, or set up memory for this project. Writes to ~/.mehmory (outside the project), so Claude Code may prompt for permission.
Stop mehmory capturing and injecting for the rest of this session — no inbox writes, no context injection, no pointers. Use when the user says pause memory, stop capturing, mute mehmory, or is about to work on something they do not want remembered. Writes one flag file under ~/.mehmory/.state (outside the project), so Claude Code may prompt for permission. Reversible with /mehmory:resume.
Turn mehmory capture and injection back on for this session after /mehmory:pause. Use when the user says resume memory, unpause, or start capturing again. Clears one flag under ~/.mehmory/.state (outside the project), so Claude Code may prompt for permission. It never re-enables a hook that was switched off in config.json — that stays the user's explicit choice.