Recall: Project & Cross-Project Memory

Overview

Recall is an opt-in memory layer. When you enable it for a project, it composes a focused brief from the project's Markdown vault and injects it into the agent before each prompt, then harvests one memory note per commit — anchored to that commit's diff — so hard-won decisions, gotchas, and conventions persist across sessions instead of being re-explained every time.

Notes are plain Markdown files in <project>/.recall/, openable in Obsidian or any editor. Two background workers do the work: an Enricher that composes the pre-prompt brief and a Harvester that writes the per-commit note.

What You See

Recall has no always-on panel. It surfaces in two places:

• Settings → Recall (Brain icon) — the control surface. It holds a master Enable Recall toggle, a Mode dropdown, a per-project vault health summary (indexed note count, a notes-by-type breakdown, harvests logged, and the last-indexed timestamp), and three actions: Run cold-start seed, Reindex, and Open vault in Finder/Explorer or Obsidian.
• In the background — when Recall is on, the Enricher runs before prompts and the Harvester runs on commit. They work silently; failures are logged and, in the default mode, never block your prompt or commit.

How to Open / Access

Open Settings with Cmd/Ctrl , and select the Recall tab. Vault actions operate on the currently active project, so open a project first. If no project is open, the tab shows "Open a project to manage its Recall vault."

Modes

User Actions

• Enable Recall — the master switch. Off by default; opt in per project. Changes on this tab save immediately, so flipping the toggle takes effect right away.
• Run cold-start seed — bootstraps the vault for an existing project. It ingests existing memory files and ADRs, seeds hotspot/landmine and co-change-pattern notes from git history, writes a manifest, and indexes the result. The toast reports notes indexed, elapsed time, and the manifest outcome.
• Reindex — re-parses the .recall/ vault into the local SQLite index. Use it after you edit notes by hand in Obsidian.
• Open vault — reveals <project>/.recall/ in your file manager (Finder on macOS, File Explorer on Windows) or Obsidian.

States

Configuration

The Settings tab ships the minimum-viable controls: enable, mode, and the vault actions. For now, power-user fields live in settings.json under a recall object; a fuller Recall settings panel is planned for a later release.

Privacy

Tips

• Seed an existing codebase first. Run cold-start seed once so the first brief has history to draw on instead of starting empty.
• Leave Mode on Suggested unless you specifically want the Enricher to be a hard gate. Enforced blocks prompts (and Self-Drive) if the Enricher model is unreachable.
• Notes are plain Markdown. Open the vault in Obsidian to read, edit, or prune them, then click Reindex.
• Override the default model if you want. The Enricher and Harvester use the inexpensive gemini-3.1-flash-lite; point them at a stronger model in settings.json if you want it writing your memory notes.

Related Articles

• Self-Drive: Autonomous Implementation — Enforced mode gates Self-Drive on the Enricher completing
• Per-Task Agent Routing — Recall injects its brief into whichever agent handles the prompt
• Session Persistence — How your work carries across sessions alongside Recall's memory
• Settings Reference — Every Recall configuration field in one place