recall

name	recall
description	Pull relevant findings stashed from past sessions — on demand. Triggers on: recall, remember, what did I learn, prior session, past findings, did I hit this before, what do we know about.
argument-hint	<topic to recall | leave empty for recent>

Recall

IMPORTANT: Start your response by telling the user:

Recall — Searching cross-session memory for findings related to your query.

What It Does

/recall is the on-demand companion to the automatic SessionStart recall. It searches the findings stashed by the Stop hook across past sessions (file backend by default; Redis AMS when connected) and surfaces the most relevant ones, formatted for reading.

• With a query (/recall AMS event loop): keyword + recency search, same-project findings ranked first.
• No query (/recall): the most recent findings for this project.

How To Run It

Recall is exposed through attune.memory.session_stash. Run the appropriate snippet via Bash from the project root, then present the results as a readable list (newest / most-relevant first), grouped or annotated by their [type].

With a query:

python -c "import json, os; from attune.memory.session_stash import recall_entries; print(json.dumps(recall_entries(os.environ['Q'], top_k=8, cwd=os.getcwd()), ensure_ascii=False))"

Pass the user's topic as the Q environment variable (avoids quoting issues), e.g. Q="AMS event loop" python -c "...".

No query (recent):

python -c "import json, os; from attune.memory.session_stash import recent_entries; print(json.dumps(recent_entries(top_k=8, cwd=os.getcwd()), ensure_ascii=False))"

Each result is a dict with text, topics (carrying type:<kind> and cwd:<path>), cwd, and session_id. Render them as:

- [decision] <text>
- [bug] <text>

When Nothing Comes Back

An empty list means no matching findings yet (the store fills as the Stop hook stashes findings over sessions), or no searchable backend is installed. Say so plainly — do not invent findings. Suggest the user keep working; the soak fills the store over time.

Promote A Keeper

If a recalled finding is worth keeping permanently, the user can promote it into curated memory with /remember — the durable, human-curated tier above this raw cross-session stash.