sparkecoder 0.1.55 → 0.1.56

package/dist/{index-dJv_dqUq.d.ts → index-CqKMYoJv.d.ts}

@@ -1,7 +1,7 @@
 import { ModelMessage, streamText } from 'ai';
 import { S as Session, b as ToolExecution } from './schema-NcQknWCg.js';
 import { z } from 'zod';
-import { B as BashToolProgress, W as WriteFileProgress, S as SearchToolProgress } from './search-DrztQ_iP.js';
+import { B as BashToolProgress, W as WriteFileProgress, S as SearchToolProgress } from './search-CZsTAZ90.js';
 
 declare const ToolApprovalConfigSchema: z.ZodObject<{
     bash: z.ZodDefault<z.ZodOptional<z.ZodBoolean>>;

package/dist/index.d.ts

@@ -1,11 +1,11 @@
-import { R as ResolvedConfig } from './index-dJv_dqUq.js';
-export { A as Agent, a as AgentOptions, b as AgentRunOptions, c as AgentStreamResult, S as SparkcoderConfig, T as ToolApprovalConfig } from './index-dJv_dqUq.js';
+import { R as ResolvedConfig } from './index-CqKMYoJv.js';
+export { A as Agent, a as AgentOptions, b as AgentRunOptions, c as AgentStreamResult, S as SparkcoderConfig, T as ToolApprovalConfig } from './index-CqKMYoJv.js';
 export { ServerOptions, createApp, startServer, stopServer } from './server/index.js';
 export { checkpointQueries, closeDatabase, fileBackupQueries, getDb, initDatabase, messageQueries, sessionQueries, skillQueries, todoQueries, toolExecutionQueries } from './db/index.js';
 import { F as FileBackup, C as Checkpoint } from './schema-NcQknWCg.js';
 export { a as Message, M as ModelMessage, S as Session, q as SessionConfig, f as Terminal, T as TodoItem, b as ToolExecution } from './schema-NcQknWCg.js';
 export { createLoadSkillTool, createReadFileTool, createTodoTool, createTools } from './tools/index.js';
-export { c as createBashTool, a as createWriteFileTool } from './search-DrztQ_iP.js';
+export { c as createBashTool, a as createWriteFileTool } from './search-CZsTAZ90.js';
 import 'ai';
 import 'zod';
 import 'hono/types';

package/dist/index.js

@@ -4194,14 +4194,10 @@ The Explore agent will explore the codebase and return a summary of findings.
 This is more thorough than a simple grep because it can follow references and understand context.
 It also has access to semantic search to find code by meaning, not just text.
 
-Examples:
-- "Find all React components that use the useState hook"
-- "Where is the authentication logic implemented?"
-- "Find all API routes and their handlers"
-- "Search for usages of the UserService class"`,
+CRITICAL: The explore agent has ZERO context. It cannot see the conversation, the user's message, devtools data, or any prior context. You MUST pass ALL relevant context via the "context" parameter. If the user selected a component (component name, file path, HTML, component stack) or there is a <devtools-context> block, you MUST copy that information into the "context" field verbatim. Without it the explore agent is searching blind.`,
     inputSchema: z10.object({
       query: z10.string().describe("What to search for. Be specific about what you're looking for."),
-      context: z10.string().optional().describe("Optional additional context about why you need this information.")
+      context: z10.string().describe("ALL context the explore agent needs. It has ZERO context on its own - no conversation history, no devtools data, nothing. You MUST include: any selected component info (name, file path, HTML, component stack), any <devtools-context> block (page URL, path, viewport), and any other relevant details from the user message. The explore agent literally only sees the query and this context field.")
     }),
     execute: async ({ query, context }, toolOptions) => {
       const toolCallId = toolOptions.toolCallId || `explore_agent_${Date.now()}`;
@@ -4529,6 +4525,11 @@ Use this proactively after making code changes to catch errors early.
 
 **Choose the right search approach:**
 
+0. **Use paths to your advantage \u2014 skip searching if you already have what you need.**
+   - If the user selected a component via devtools and you can see the component name, file path, and/or line number, you ALREADY know where the code is. Just use \`read_file\` to read that file directly \u2014 do NOT call \`explore_agent\` to "find" something you already have the location of.
+   - If you received a **page path** (e.g. \`/dashboard\`, \`/settings/profile\`), map it to the corresponding file in the project structure. In Next.js this means \`app/dashboard/page.tsx\`, \`app/settings/profile/page.tsx\`, etc. In other frameworks, check the routing convention (e.g. \`pages/\`, \`src/routes/\`). Use \`read_file\` on the mapped path directly.
+   - If the file path doesn't exist or \`read_file\` fails, fall back to grep to locate it (e.g. \`rg "ComponentName" --type ts -l\`) since devtools paths can sometimes be slightly off or truncated.
+   - Read up and down component trees when you have the file path or page path to find what you're looking for.
 1. **Use the \`explore_agent\` tool (Explore agent)** for:
    - Semantic/exploratory questions: "How does authentication work?", "Where is user data processed?"
    - Finding code by meaning or concept, not exact text
@@ -4538,11 +4539,12 @@ Use this proactively after making code changes to catch errors early.
    
    The Explore agent is a mini-agent that intelligently explores the codebase, reads relevant files, and returns a summary of what it found. It's best for understanding and discovery.
 
-   **IMPORTANT: The Explore agent has NO context on its own.** When you call \`explore_agent\`, you MUST pass along any relevant context the user has given you via the \`context\` parameter. In particular:
-   - If the user selected a component via devtools (you'll see component name, file path, HTML, component stack in their message), pass ALL of that to the explore agent's \`context\` field.
-   - If there is a \`<devtools-context>\` block with the current page URL, path, and viewport, include that too.
-   - If the user references "this page", "this component", "this button", etc., the explore agent needs the component name, file path, and page path to know what to search for.
-   - The explore agent cannot see the conversation history. The \`query\` and \`context\` fields are the ONLY information it receives.
+   **MANDATORY \u2014 The Explore agent has ZERO context.** It cannot see the conversation, the user's messages, devtools data, or anything else. The \`query\` and \`context\` fields are the ONLY information it receives. Every time you call \`explore_agent\`, you MUST populate the \`context\` field with ALL relevant information:
+   - Copy the ENTIRE \`<devtools-context>\` block (page URL, path, viewport) if one exists in the user's message.
+   - Copy ALL selected component info (component name, file path, line number, HTML snippet, component stack) if the user selected something via devtools.
+   - Include any file paths, component names, or page names the user mentioned.
+   - If you skip the \`context\` field, the explore agent is searching completely blind and will waste time guessing.
+   - NEVER call \`explore_agent\` with only a \`query\` and no \`context\` when the user's message contains devtools or component information.
 
 2. **Use direct commands (grep/rg, find)** for:
    - Exact string matches: \`rg "functionName"\`, \`rg "class MyClass"\`
@@ -4551,7 +4553,8 @@ Use this proactively after making code changes to catch errors early.
    - Counting occurrences or listing all matches
 
 **Examples:**
-- "Where is the API authentication handled?" \u2192 Use \`explore_agent\` tool
+- User selected \`<LandingButton>\` at \`src/components/LandingButton.tsx:12\` \u2192 Just \`read_file("src/components/LandingButton.tsx")\`. Do NOT call explore_agent.
+- "Where is the API authentication handled?" (no file path given) \u2192 Use \`explore_agent\` tool
 - "Find all usages of getUserById" \u2192 Use \`rg "getUserById"\`
 - "How does the payment flow work?" \u2192 Use \`explore_agent\` tool
 - "Find files named config" \u2192 Use \`find . -name "*config*"\`