sparkecoder 0.1.27 → 0.1.28

package/dist/cli.js

@@ -3434,13 +3434,13 @@ var MAX_OUTPUT_CHARS4 = 2e4;
 var MAX_FILE_SIZE2 = 2 * 1024 * 1024;
 var SearchSubagent = class extends Subagent {
   type = "search";
-  name = "Search Agent";
+  name = "Explore Agent";
   constructor(model) {
     super(model || SUBAGENT_MODELS.search);
     this.maxSteps = 15;
   }
   getSystemPrompt(options) {
-    return `You are a specialized search agent for exploring codebases. Your job is to find relevant code, files, and patterns based on the user's query.
+    return `You are an Explore agent for codebase discovery. Your job is to map the structure, find relevant files, and surface connections based on the user's query.
 
 Working Directory: ${options.workingDirectory}
 
@@ -3450,9 +3450,9 @@ You have these tools available:
 - read_file: Read contents of a specific file
 - list_dir: List directory contents
 
-## Strategy - Search in Parallel
+## Strategy - Explore in Parallel
 
-IMPORTANT: When searching, run MULTIPLE searches in PARALLEL to cover different variations and related terms. Don't search sequentially - batch your searches together!
+IMPORTANT: When exploring, run MULTIPLE searches in PARALLEL to cover different variations and related terms. Don't explore sequentially - batch your searches together!
 
 For example, if asked "how does authentication work":
 - Search for "auth", "login", "session", "jwt", "token" all at once
@@ -3474,10 +3474,11 @@ For example, if asked "how does authentication work":
    - Search content: patterns, function names, class names
 
 ## Execution Flow
-1. First, run 2-4 parallel searches covering different angles of the query
-2. Review results and identify the most relevant files
-3. Read the key files to understand the full context
-4. Provide a clear summary with exact file paths and line numbers
+1. Start broad: list likely directories or entry points if the query is open-ended
+2. Run 2-4 parallel searches covering different angles of the query
+3. Review results and identify the most relevant files
+4. Read the key files to understand the full context
+5. Provide a clear summary with exact file paths and line numbers
 
 Be efficient - you have limited steps. Maximize coverage with parallel tool calls.
 
@@ -3486,6 +3487,7 @@ When done, provide a summary with:
 - Key files/locations found (with full paths)
 - Relevant code snippets showing the important parts
 - How the pieces connect together
+- Suggested next files to inspect (if more depth is needed)
 
 Keep your responses concise and focused on actionable information.`;
   }
@@ -3736,13 +3738,13 @@ function createSearchSubagent(model) {
 var MAX_RESULT_CHARS = 8e3;
 function createSearchTool(options) {
   return tool8({
-    description: `Delegate a search task to a specialized search agent. Use this when you need to:
+    description: `Delegate a search task to a specialized Explore agent. Use this when you need to:
 - Find files or code matching a pattern
 - Explore the codebase structure
 - Search for specific functions, classes, or variables
 - Understand how a feature is implemented
 
-The search agent will explore the codebase and return a summary of findings.
+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.
 
 Examples:
@@ -3804,7 +3806,7 @@ Context: ${context}` : query;
           };
         }
         const searchResult = result.result;
-        let formattedResult = `## Search Results
+        let formattedResult = `## Explore Results
 
 `;
         formattedResult += `**Summary:** ${searchResult.summary}
@@ -4562,7 +4564,7 @@ async function indexRepository(options) {
       skippedChunks: 0,
       failedChunks: 0,
       duration: Date.now() - startTime,
-      errors: [{ file: "", error: "Vector Gateway not configured. Set VECTOR_REDIS_URL or configure vectorGateway in sparkecoder.config.json" }]
+      errors: [{ file: "", error: "Remote server not configured. Set SPARKECODER_REMOTE_URL/SPARKECODER_AUTH_KEY or remoteServer in sparkecoder.config.json" }]
     };
   }
   try {
@@ -4699,7 +4701,7 @@ async function getIndexStatus(workingDirectory) {
     workingDirectory,
     config.resolvedVectorGateway.namespace
   );
-  const isConfigured = !!config.resolvedVectorGateway.redisUrl;
+  const isConfigured = config.resolvedRemoteServer.isConfigured;
   if (!namespace) {
     return {
       namespace: "",
@@ -4787,7 +4789,7 @@ Returns matching code snippets with file paths, line numbers, and relevance scor
         if (!client) {
           return {
             success: false,
-            error: 'Vector Gateway not configured. Run "sparkecoder index --status" for setup instructions.'
+            error: "Remote server not configured. Set SPARKECODER_REMOTE_URL/SPARKECODER_AUTH_KEY or run sparkecoder to register."
           };
         }
         try {
@@ -4986,7 +4988,7 @@ You have access to powerful tools for:
 - **linter**: Check files for type errors and lint issues (TypeScript, JavaScript, TSX, JSX)
 - **todo**: Manage your task list to track progress on complex operations
 - **load_skill**: Load specialized knowledge documents for specific tasks
-- **search**: Semantic search using a subagent - for exploratory questions and finding code by meaning
+- **search**: Explore agent for semantic discovery - for exploratory questions and finding code by meaning
 
 
 IMPORTANT: If you have zero context of where you are working, always explore it first to understand the structure before doing things for the user.
@@ -5080,14 +5082,14 @@ Use this proactively after making code changes to catch errors early.
 
 **Choose the right search approach:**
 
-1. **Use the \`search\` tool (subagent)** for:
+1. **Use the \`search\` 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
    - Understanding how features are implemented across multiple files
    - Exploring unfamiliar parts of the codebase
    - Questions like "where", "how", "what does X do"
    
-   The search subagent 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.
+   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.
 
 2. **Use direct commands (grep/rg, find)** for:
    - Exact string matches: \`rg "functionName"\`, \`rg "class MyClass"\`
@@ -9302,8 +9304,9 @@ program.command("config").description("Show current configuration").option("-c,
 program.command("index").description("Index repository for semantic search").option("--status", "Show index status instead of indexing").option("--full", "Force full re-index (ignore existing embeddings)").option("-w, --working-dir <path>", "Working directory (defaults to current directory)").option("-c, --config <path>", "Path to config file").option("-v, --verbose", "Show detailed progress").action(async (options) => {
   try {
     const workingDir = options.workingDir ? resolve10(options.workingDir) : process.cwd();
-    const config = loadConfig(options.config, workingDir);
-    if (!config.resolvedRemoteServer.url) {
+    let config = loadConfig(options.config, workingDir);
+    const remoteUrl = config.resolvedRemoteServer.url;
+    if (!remoteUrl) {
       console.error(chalk.red("Error: Remote server not configured"));
       console.log(chalk.dim("Set REMOTE_SERVER_URL environment variable or remoteServer.url in config"));
       process.exit(1);
@@ -9311,9 +9314,16 @@ program.command("index").description("Index repository for semantic search").opt
     let authKey3 = config.resolvedRemoteServer.authKey;
     if (!authKey3) {
       console.log(chalk.dim("Registering with remote server..."));
-      authKey3 = await ensureRemoteAuthKey(config.resolvedRemoteServer.url);
+      authKey3 = await ensureRemoteAuthKey(remoteUrl);
+      config = loadConfig(options.config, workingDir);
+      authKey3 = config.resolvedRemoteServer.authKey || authKey3;
     }
-    initDatabase({ url: config.resolvedRemoteServer.url, authKey: authKey3 });
+    if (!authKey3) {
+      console.error(chalk.red("Error: Remote auth key not available"));
+      console.log(chalk.dim("Set SPARKECODER_AUTH_KEY or run sparkecoder to register with the remote server"));
+      process.exit(1);
+    }
+    initDatabase({ url: remoteUrl, authKey: authKey3 });
     if (!isGitRepository(workingDir)) {
       console.error(chalk.red("Error: Not a git repository"));
       console.log(chalk.dim("Semantic indexing requires a git repository with a remote configured."));
@@ -9340,24 +9350,12 @@ program.command("index").description("Index repository for semantic search").opt
         console.log(`  Last incremental: ${chalk.dim(status.lastIncrementalIndex.toLocaleString())}`);
       }
       if (!status.isConfigured) {
-        console.log(chalk.yellow("\n\u26A0 Vector Gateway not configured"));
-        console.log(chalk.dim("  Set VECTOR_REDIS_URL environment variable or configure vectorGateway in sparkecoder.config.json"));
+        console.log(chalk.yellow("\n\u26A0 Remote server not configured"));
+        console.log(chalk.dim("  Set SPARKECODER_REMOTE_URL/SPARKECODER_AUTH_KEY or remoteServer in sparkecoder.config.json"));
       }
       console.log();
       return;
     }
-    if (!config.resolvedVectorGateway.redisUrl) {
-      console.error(chalk.red("Error: Vector Gateway not configured"));
-      console.log(chalk.dim("Set VECTOR_REDIS_URL environment variable or configure vectorGateway in sparkecoder.config.json"));
-      console.log(chalk.dim("\nExample sparkecoder.config.json:"));
-      console.log(chalk.dim(`{
-  "vectorGateway": {
-    "redisUrl": "redis://your-redis-host:6379",
-    "httpUrl": "http://your-vector-gateway:8080"
-  }
-}`));
-      process.exit(1);
-    }
     console.log(chalk.bold(`
 Indexing ${chalk.cyan(namespace)}...
 `));