You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"A tool to extract relevant information from the thread and select relevant files for another agent to continue the conversation. Use this tool to identify the most important context and files needed.",
18
+
inputSchema: z.object({
19
+
text: z.string().describe(PROMPT_HANDOFF),
20
+
files: z
21
+
.string()
22
+
.array()
23
+
.describe(
24
+
[
25
+
"An array of file or directory paths (workspace-relative) that are relevant to accomplishing the goal.",
26
+
"",
27
+
'IMPORTANT: Return as a JSON array of strings, e.g., ["packages/core/src/session/message-v2.ts", "packages/core/src/session/prompt/handoff.txt"]',
28
+
"",
29
+
"Rules:",
30
+
"- Maximum 10 files. Only include the most critical files needed for the task.",
31
+
"- You can include directories if multiple files from that directory are needed",
32
+
"- Prioritize by importance and relevance. PUT THE MOST IMPORTANT FILES FIRST.",
Extract relevant context from the conversation above for continuing this work. Write from my perspective (first person: "I did...", "I told you...").
2
+
3
+
Consider what would be useful to know based on my request below. Questions that might be relevant:
4
+
5
+
- What did I just do or implement?
6
+
- What instructions did I already give you which are still relevant (e.g. follow patterns in the codebase)?
7
+
- What files did I already tell you that's important or that I am working on (and should continue working on)?
8
+
- Did I provide a plan or spec that should be included?
9
+
- What did I already tell you that's important (certain libraries, patterns, constraints, preferences)?
10
+
- What important technical details did I discover (APIs, methods, patterns)?
11
+
- What caveats, limitations, or open questions did I find?
12
+
13
+
Extract what matters for the specific request below. Don't answer questions that aren't relevant. Pick an appropriate length based on the complexity of the request.
14
+
15
+
Focus on capabilities and behavior, not file-by-file changes. Avoid excessive implementation details (variable names, storage keys, constants) unless critical.
16
+
17
+
Format: Plain text with bullets. No markdown headers, no bold/italic, no code fences. Use workspace-relative paths for files.
0 commit comments