You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 226d27b
Browse filesBrowse the repository at this point in the historyBrowse files
recall_sessions searched only the one-line outcomes; now it also scans the
conversations themselves, so a match that never made it into the summary — a
library, a decision, an error mentioned mid-session — is still found and comes
back with a cited snippet from the actual transcript.
- sessionMemory.js: queryTerms (shared normalization) + snippetFor (pure — find
the first matching turn, return a short role-prefixed citation).
- sessions.js: recall now scores by journal metadata (summary/title/files, all
sessions) AND a bounded deep scan of recent transcripts (scanMax, default 40),
merging so a transcript-only hit still surfaces with its snippet; a metadata
hit outranks a body-only hit.
- extension.js: the recall result cites the snippet under each outcome.
- agent.js: RECALL_TOOL description notes it searches conversations + returns
snippets.
- tests: +1 sessionMemory (snippet extraction), +1 sessions (deep scan finds a
transcript-only match with a snippet). 31 files green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
// Cross-session memory recall (docs/levelcode-sessions-memory.md). Added to a run's tools ONLY when the host
74
74
// wires ctx.recallSessions (memory + the recall setting on), so it costs nothing otherwise. Read-only and
75
75
// instant like use_skill — it searches the project's OWN past-session outcomes, never the file system.
76
-
constRECALL_TOOL={name: 'recall_sessions',description: 'Search THIS project\'s past sessions for relevant earlier work — their recorded outcomes (what was built/fixed/decided) and the files they touched. Use when the user refers to earlier work ("what did we do about refunds?", "did we already fix the webhook?") or when prior context would clearly help before you start. Returns cited past-session outcomes with dates; treat them as memory — informative but possibly stale, so verify against the current code.',input_schema: {type: 'object',properties: {query: {type: 'string',description: 'keywords or a short question, e.g. "refund retries" or "MCP timeline rail"'}},required: ['query']}};
76
+
constRECALL_TOOL={name: 'recall_sessions',description: 'Search THIS project\'s past sessions for relevant earlier work — their recorded outcomes (what was built/fixed/decided), the files they touched, and the conversations themselves. Use when the user refers to earlier work ("what did we do about refunds?", "did we already fix the webhook?") or when prior context would clearly help before you start. Returns cited past-session outcomes (with a matching transcript snippet when the match is deep in the conversation) and dates; treat them as memory — informative but possibly stale, so verify against the current code.',input_schema: {type: 'object',properties: {query: {type: 'string',description: 'keywords or a short question, e.g. "refund retries" or "MCP timeline rail"'}},required: ['query']}};
77
77
78
78
// How much of a background command's accumulated output the sniffers re-read on each chunk. Generous
79
79
// next to any single log line, so a url split across chunk boundaries is still found, yet small enough
0 commit comments