Skip to main content
Your persistent memory across all AI tools. This is the unified read tool — it handles search, file history, and entity overview based on which parameters you provide.
v0.7.0: recall replaces the previous recall + recall_file + list_entities tools. Mode is auto-detected from params.

Modes

Search (provide query)

Returns memories ranked by a composite score of relevance, heat, momentum, and importance.

File history (provide path)

Returns complete edit history of a file across all sessions, with per-edit user-intent context.
When both path and query are provided, results from file history and memory search are merged.

Entity overview (no params)

Returns entity list sorted by momentum — the cheapest “what do I know?” primitive.

Parameters

Search mode

string
What you want to remember. Free-text, entity name, or FTS5 MATCH expression.
string
Narrow results to a specific entity.
string
Filter by memory layer. Accepts aliases (e.g. warnings -> caveat).
string
Filter by cognitive altitude: mission, strategy, architecture, implementation.
string
Filter by memory type: question, comparison, decision, work, outcome, learning, note.
string
Filter by lifecycle state: open, decided, in_progress, done, stalled, parked, superseded.
string
Filter by thread ID — returns all memories in a decision chain or session group.
string
Filter by heat band: hot, warm, cold, frozen.
number
default:"2000"
Approximate token budget. Iteration stops when this budget is consumed or limit is reached, whichever comes first.
number
Hard cap on number of memories returned.
number
default:"0"
Skip this many top results (pagination). Use has_more from prior response to decide next offset.
boolean
default:"true"
Set false for preview / listing queries that should not bump heat scores.

File history mode

string
File path substring to match against edit history. Can be a filename (search-services.ts), partial path (src/db/), or full absolute path.

Ranking (search mode)

Memories are ranked by a composite score:

Response

Search mode

Each memory in the response includes:
  • match_reasons — array explaining why this memory ranked (e.g. content_match_fts, entity_name_match, heat:hot, pinned, caveat_protected)
  • score_breakdown — individual scores for transparency
  • has_more — boolean indicating if more results exist beyond the current page
  • stopped_by — whether iteration stopped at tokens, limit, or end

File history mode

Entity overview mode

Each entity includes: name, kind, memory_count, layer breakdown (goal_count, caveat_count, etc.), momentum_score.
Dual search: Recall uses both FTS5 full-text search (BM25-ranked, trigram tokenizer) and LIKE fallback, merging and deduplicating results. This ensures both exact and fuzzy matches are found, including Japanese text.

Migration from pre-v0.7