chat-recalllisted

Recall past AI-coding work — prior sessions, decisions, and project history — through the chat-recall MCP tools (recall_*). Use when the user says "continue" / "pick up where we left off", "did we decide X", "remember when we…", "what was I doing", "what do you know about this project/me", or otherwise references earlier work that is not in the current context. Also the entry point for the surfaces no focused skill owns: team activity ("what is my team working on"), the ranked findings views ("what should I fix next", "what should I tell Claude about this repo"), and index health ("is chat-recall working", "re-index my sessions"). Leaked secrets go to chat-recall-security and the task board to chat-recall-tasks. This is the hub: it routes to the focused chat-recall skills and lists every recall_* tool. Reach for it whenever the answer lives in PAST work rather than the files in front of you.
munhq/chat-recall · ★ 2 · AI & Automation · score 65

Install: claude install-skill munhq/chat-recall

# chat-recall — cross-session memory for AI coding chat-recall indexes your Claude Code, Gemini, OpenCode, Codex and Antigravity sessions — plus plans, tasks, CLAUDE.md files, shell history and agent diaries — into a searchable server with a temporal knowledge graph. When a request depends on something that happened in an *earlier* session (a decision, a past fix, "what were we doing"), don't guess or ask the user to re-explain — recall it. All tools are MCP tools on the `chat-recall` server, named `<tool>`. **Reads are safe to call proactively. Writes are not.** Everything below is a read except these, which change stored memory or state — treat each as an edit and apply the test in `chat-recall-memory` before calling one: `recall_kg_add`, `recall_kg_invalidate`, `recall_decision_record`, `recall_diary_write`, `recall_set`, `recall_task_create`, `recall_task_update`, `recall_task_comment`, `recall_task_policy`, `recall_security_dismiss`, `recall_rename_session`, `recall_regenerate_summary`, `recall_reclassify`, `recall_index`, `recall_code_index`. Two of those are in a class of their own — they REMOVE what the user has stored, and the host will ask before each call because they are deliberately not on the auto-approve list. `recall_forget` deletes one conversation from the server permanently (their own transcript file is untouched — say so). `recall_exclude_path` stops a path syncing, here and on their other devices. Both take `confirm: true`, and you pass it only when t