Session Recall

Recover missing conversation context autonomously. Never ask the user "what are you talking about?" until all steps are exhausted.

When This Triggers

• An incoming message doesn't match the current session context
• Session starts after compaction (.jsonl.reset exists)
• User references something not in current context window
• User references a topic from another channel or a cron-delivered notification
• Thread reply arrives without visible parent context

Recovery Flow

Execute steps in order. Stop early if sufficient context is found.

Step 0: sessions_history (fastest check)

Use sessions_history to retrieve recent messages for the current channel. This requires no file I/O and is the quickest way to recover recent context.