Recall plugin
Fully local project memory for Claude Code: a session log and a condensed summary with no API keys and nothing sent out
- 768 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads session transcripts that may contain code and secrets
- Writes the log and summary to project files
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/recallDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads session transcripts that may contain code and secrets
- Writes the log and summary to project files
This is third-party code. Review the repository files before installing.
What it does
Recall solves the cold-start problem: Claude Code begins every session fresh, while Recall keeps a local log of the work and condenses it into a resume-ready summary right on your machine. Two files go into .recall/: history.md with the full session log and context.md with a short summary of the goal, what was done, which files were touched and where you stopped. The condensing is done by a vendored classical Python summarizer, with no model call, keys or local model. Nothing leaves your machine, and the memory is plain markdown you can read and share across agents.
Who it is for. For people running Claude Code on a subscription who do not want to re-explain the project every session.
Good fit when
- You are tired of re-explaining the project at the start of each session
- You want memory that spends no tokens and never goes to the network
- You need to share context between Claude Code and OpenCode on one repo
Not a fit when
- You need semantic search over a large base rather than session summaries
- The built-in CLAUDE.md and resume are enough
Example request
Save the session memory with /recall:save and at the next start bring up where we left offLimitations
The summary is made by a deterministic local algorithm rather than an LLM, so it is simpler than a model-made one. Session logs contain code, paths and sometimes secrets, but stay on your machine. Claude Code is the first-class path; OpenCode setup is separate and opt-in.
How to disable. Uninstall via /plugin uninstall recall@recall; the project's .recall/ folder can be removed manually.
FAQ
Does Recall spend tokens?
No. The summary is built by a local Python summarizer with no model call, and a compact context.md at start saves session tokens.
Does data go to the network?
No. Logs and summaries stay in .recall/ on your machine, there is no external API, and it works offline.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin stores conversations and decisions in Markdown, updates CLAUDE.md and helps resume work in a new session.
Persistent memory for Claude Code on your own database: capture of decisions and context plus a code graph, injected into every prompt
A Claude Code environment installer: CLAUDE.md, rules, skills, agents, hooks and two-layer project memory in one script
A marketplace of eight Claude Code plugins: session memory, research, commits, skill authoring and more.
A starter kit for Claude Code: a CLAUDE.md memory-bank template with ready hooks, subagents and skills you copy into your project
Project memory and workflows for Claude Code and Codex: stories, plans, session handovers and review records kept in the repo
README in short
The README describes Recall as fully local project memory for Claude Code that solves the cold start with no keys or external models. Into .recall/ it writes history.md as an append-only log and context.md as a condensed summary made by a vendored classical Python summarizer. The author contrasts Recall with CLAUDE.md and resume: it is an automatic, deterministic record of what each session did. Install is via its own marketplace or locally, with opt-in OpenCode support on the same markdown files, and the memory is fenced as untrusted data.