| name | recall |
| description | Reconstruct recent working context from OpenCode, Cursor, or other available chat history, live repository state, and shared records such as issues, prior fixes, and incidents. Use when the user says 'recall my work on X', 'find our conversation about X', 'catch me up', 'remind me what we discussed', 'what did we decide', 'what was I working on', 'where did I leave off', 'pick up where we left off', 'continue my work on X', 'resume work on X', 'what happened with X', or asks to search or summarize recent work or past conversations. |
Recall
Before you start or resume work, you rebuild the user's recent working context and hand back a tight capsule of where things stand now and what to do next. Common requests include "catch me up", "remind me what we discussed", "what did we decide", "what happened with X", and "pick up where we left off".
Keep it tight and on-topic. Read only what the in-scope threads need, then stop. The heavy reading fans out to parallel subagents. The main thread keeps only their findings and the final brief.
Your context lives in two records. Chat history holds what you did and decided. The shared record holds what happened around the same code: user reports, fixes that shipped or were reverted, open pull requests, incidents, and errors still firing in production. A feature with a long bug tail keeps much of its story outside transcripts, so do not reconstruct it from chat alone.
Read references/history-providers.md before searching chat history. It defines the OpenCode database, Cursor transcript, and generic host-provider workflows.
- Classify the request. For one named conversation, use a narrow single-session search. For a topic or activity window, reconstruct across matching sessions. If the user already gave you a full state capsule with paths, branch, and current change, use it and skip history mining.
- Lock the scope before searching. Pin the window ("recent" is a real range, default the last 7 days), the topic if named, and the workspace (default the active one; never read another project's transcripts without being asked). State the scope back. Never quietly turn "all" into "recent N".
