recalllisted

# Recall **Mission:** Restore as much relevant context as possible. Never return empty-handed. If one source has nothing, try the next. Synthesize what you find into a clear briefing so the conversation can continue naturally. ## When invoked The user ran `/recall` (possibly with a topic hint like `/recall project X status` or `/recall alice relationship analysis`) after a `/new` reset or context overrun. They want to pick up where they left off. Your job is to find that thread and hand it back to them. **Implicit recall (no `/recall` command):** A common case is a bare-pronoun follow-up right after a daily reset or `/new` — e.g. "ok deliver this", "ship it", "send that", "do it", "go ahead". The antecedent ("this", "that", "it") points at an artifact from the previous session that you no longer have in context. Treat these as recall triggers: go straight to step 2b (raw jsonl tail of the most recent prior session) and find the last assistant artifact — usually a draft, a ranked list, a proposed plan, or a pending-approval message. Then either confirm what they mean before acting, or surface the candidate artifact verbatim so they can say yes/no. Do **not** guess and execute on a deictic without verifying — the wrong "this" is worse than a clarifying question. ## What to do Work through these sources in order. **Do not stop at the first miss** — keep going until you have enough to give a useful briefing, or until all sources are exhausted. ### 1. Session search (start