claude-recalllisted

Always-on Claude Code skill that bridges Claude with an Obsidian vault for persistent project memory. Automatically loads relevant context nodes from mindmap.json before every prompt (UserPromptSubmit hook) and saves structured session notes to the vault on exit (Stop hook). Zero manual invocation — hooks fire automatically. Context is AUTO-GENERATED using the claude CLI. Claude analyzes transcripts and project files to populate mindmap.json with stack, architecture decisions, gotchas, and current state. Users never need to manually edit. The /recall command lets users trigger on-demand context updates from the terminal. MCP tools (recall_get, recall_update_node, recall_session_history, recall_mindmap) let Claude fetch deeper context mid-session. Storage: <vault>/claude-recall/projects/<project-slug>/mindmap.json (JSON graph) and sessions/YYYY-MM-DD_HH-MM.md (session notes). Project slug is derived from the directory Claude Code was launched in. Install from GitHub (one command): curl -fsSL https://raw.github
senapati484/claude-recall · ★ 6 · AI & Automation · score 69

Install: claude install-skill senapati484/claude-recall

# claude-recall Obsidian-backed persistent memory for Claude Code. Install once, works on every session. **All context is auto-generated** using a local LLM — no manual Obsidian editing required. ## Session Model A **session = one terminal session** (open terminal → close terminal or `/exit`). This is NOT per-prompt. The session marker at `~/.claude/.recall_<session_id>` prevents context re-injection after the first prompt of a session. ``` Terminal session opens → UserPromptSubmit fires → context loaded ONCE Terminal session continues → UserPromptSubmit fires → SKIPPED (marker exists) Terminal session closes → Stop hook fires → session note written, context updated ``` ## How It Works ``` Session start → load_context.py → keyword match → inject 2-3 relevant nodes Tool use → post_tool_use.py → mark_files_stale() on Edit/Write/Create Session end → save_context.py → claude CLI → update mindmap.json nodes /recall query → MCP server recall_get() → return relevant context nodes ``` Both hooks run via Claude Code hooks in `~/.claude/settings.json`. No invocation needed. The `/recall` command is invoked directly by the user during a Claude session. MCP tools are available for Claude to call mid-session for deeper context. ### Hook Events - **UserPromptSubmit**: Injects relevant context nodes based on current prompt keywords - **PostToolUse**: Marks mindmap nodes stale when files are edited (Edit, Write, MultiEdit, Create) - **Stop**: Analyzes ful