Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.linksee.app/llms.txt

Use this file to discover all available pages before exploring further.

Get the complete edit history of a file across all sessions, with per-edit user-intent context. Returns total edit count, daily breakdown, distinct user intents that drove the edits, and linked memories. Use when you need to understand WHY a file was modified historically — far more accurate than recall for file-centric questions because it queries session_file_edits (every physical edit) instead of summary memories.

​
Parameters

​
path_substring
string
required
Substring to match against file paths. Can be a filename (search-services.ts), partial path (src/db/), or full absolute path.
​
max_intents
number
default:"10"
Max distinct user-intent snippets to return.
​
scope_to_roots
boolean
default:"false"
If true, filter results to files inside the client-provided roots (MCP Roots). Skips silently when the client provides no roots.

​
Response

FieldDescription
paths_matchedList of file paths that matched the substring
total_editsTotal number of physical edits recorded
first_edit / last_editDate range of edit history
sessions_involvedNumber of distinct sessions that edited this file
daily_breakdownEdits per day, grouped by operation type
user_intentsDistinct user-intent snippets, ordered by recency
linked_memoriesRelated memories with entity name and preview

​
Example

{
  "path_substring": "globals.css",
  "max_intents": 5
}
Response: 
{
  "paths_matched": ["C:/Users/HP/linksee-site/app/globals.css"],
  "total_edits": 14,
  "first_edit": "2026-04-20",
  "last_edit": "2026-05-28",
  "sessions_involved": 3,
  "user_intents": [
    "Dark theme redesign for LP",
    "Bump card border contrast for display visibility",
    "Initial light theme setup"
  ]
}
recall_file is the “anti-Mem0 wall” feature — it connects physical file edits to the human intent behind them, something flat memory stores cannot do.