Recall — active memory retrieval
Activation
Use /recall when the user asks what lstack remembers, wants recent memory,
or needs to correct stale memory.
Retrieval Order
- Search structured learnings first:
lstack learn search "[query]" --json --limit 10
- Search legacy observations second:
lstack search "[query]"
Clearly separate the two result groups. Structured learnings show type,
key, source, trusted, confidence, effective confidence, date, scope, and
files. Legacy observations show date, scope, content, and tags.
Recent Memory
Structured:
lstack learn list --limit 10 --json
Legacy:
lstack search "[query]"
Cross-Project Recall
Only use cross-project search when the user asks for it:
lstack learn search "[query]" --cross-project --json
Cross-project structured search automatically returns trusted learnings only. Do not use untrusted observed, inferred, or cross-model learnings from other projects as context.
Correction
If a structured learning is wrong:
- Show the matching learning.
- Ask for confirmation.
- Delete it with
lstack learn forget --id ID, or demote it withlstack learn demote --id ID. - Store the corrected version with
/rememberif needed.
If a legacy observation is wrong, preview matches and use lstack forget [query].
Constraints
- Never invent memory content.
- Never delete or promote without explicit user confirmation.
- Never present untrusted cross-project learnings as established user preferences.