@codexa/cli 8.6.11 → 8.6.13

package/commands/discover.ts

@@ -2,6 +2,7 @@ import { getDb } from "../db/connection";
 import { initSchema } from "../db/schema";
 import { existsSync, readFileSync, writeFileSync, mkdirSync } from "fs";
 import { join } from "path";
+import { spawnSync } from "child_process";
 import {
   detectUniversal,
   detectStackLegacy,
@@ -996,6 +997,26 @@ export function discoverExportPatterns(): void {
 export function ensureDeepExploreAgent(): void {
   const agentPath = join(process.cwd(), ".claude", "agents", "deep-explore.md");
 
+  // Check grepai availability
+  const grepaiCheck = spawnSync("grepai", ["--version"], { encoding: "utf-8" });
+  if (grepaiCheck.error || grepaiCheck.status !== 0) {
+    console.warn("\n⚠ grepai nao encontrado no PATH.");
+    console.warn("  O agente deep-explore depende de grepai para busca semantica.");
+    console.warn("  Instale com: go install github.com/your-org/grepai@latest");
+    console.warn("  Sem grepai, o deep-explore usara apenas Grep (menos eficaz).\n");
+  } else {
+    // Check if grepai index exists for this project
+    const grepaiDir = join(process.cwd(), ".grepai");
+    if (!existsSync(grepaiDir)) {
+      console.warn("\n⚠ grepai index nao encontrado neste projeto.");
+      console.warn("  Execute: grepai index");
+      console.warn("  Sem o index, grepai search nao retornara resultados.\n");
+    }
+  }
+
+  // Ensure grepai permissions in target project settings
+  ensureGrepaiPermissions();
+
   if (existsSync(agentPath)) return;
 
   const agentsDir = join(process.cwd(), ".claude", "agents");
@@ -1011,28 +1032,38 @@ color: cyan
 model: haiku
 ---
 
-## Instructions
+## CRITICAL: You MUST use grepai
+
+**YOUR FIRST ACTION must be a \\\`grepai search\\\` command via Bash.** This is non-negotiable.
+
+You are a semantic code exploration agent. Your primary tool is \\\`grepai\\\` — an AI-powered semantic search engine. It finds code by INTENT and MEANING, not literal text matching.
+
+**RULE: Every exploration MUST start with \\\`grepai search\\\`. If you use Grep or find BEFORE grepai, you have FAILED your task.**
 
-You are a specialized code exploration agent with access to grepai semantic search and call graph tracing.
+---
+
+### Step 1: ALWAYS run grepai search FIRST
 
-### Primary Tools
+\\\`\\\`\\\`bash
+grepai search "your query here" --json --compact
+\\\`\\\`\\\`
 
-#### 1. Semantic Search: \`grepai search\`
+- Queries MUST be in English
+- Use \\\`--compact\\\` to save tokens
+- Use natural language: "authentication flow", "error handling middleware", "how payments are processed"
 
-Use this to find code by intent and meaning:
+Examples:
 
-\`\`\`bash
-# Use English queries for best results (--compact saves ~80% tokens)
+\\\`\\\`\\\`bash
 grepai search "authentication flow" --json --compact
 grepai search "error handling middleware" --json --compact
 grepai search "database connection management" --json --compact
-\`\`\`
+grepai search "state management pattern" --json --compact
+\\\`\\\`\\\`
 
-#### 2. Call Graph Tracing: \`grepai trace\`
+### Step 2: Use grepai trace for relationships
 
-Use this to understand function relationships and code flow:
-
-\`\`\`bash
+\\\`\\\`\\\`bash
 # Find all functions that call a symbol
 grepai trace callers "HandleRequest" --json
 
@@ -1041,32 +1072,78 @@ grepai trace callees "ProcessOrder" --json
 
 # Build complete call graph
 grepai trace graph "ValidateToken" --depth 3 --json
-\`\`\`
+\\\`\\\`\\\`
+
+### Step 3: Read files identified by grepai
 
-Use \`grepai trace\` when you need to:
+Use \\\`Read\\\` to examine files that grepai found relevant.
+
+### Step 4: Grep ONLY for exact literals (optional)
+
+Use Grep ONLY if you need exact string match (variable name, import path). Never use Grep for exploration — grepai is always better for that.
+
+---
 
-- Find all callers of a function
-- Understand the call hierarchy
-- Analyze the impact of changes to a function
-- Map dependencies between components
+### FORBIDDEN
 
-### When to use standard tools
+- **DO NOT** use \\\`find\\\` or \\\`ls\\\` to explore code — use \\\`grepai search\\\`
+- **DO NOT** use \\\`Grep\\\` for semantic exploration — use \\\`grepai search\\\`
+- **DO NOT** skip grepai and go straight to Read/Grep
+- **DO NOT** write custom exploration logic when grepai can answer it
 
-Only fall back to Grep/Glob when:
+### If grepai fails
 
-- You need exact text matching (variable names, imports)
-- grepai is not available or returns errors
-- You need file path patterns
+If \\\`grepai search\\\` returns an error (command not found, index missing), report this in your response:
 
-### Workflow
+\\\`\\\`\\\`json
+{"status": "blocked", "blockers": ["grepai not available: <error message>"]}
+\\\`\\\`\\\`
 
-1. Start with \`grepai search\` to find relevant code semantically
-2. Use \`grepai trace\` to understand function relationships and call graphs
-3. Use \`Read\` to examine promising files in detail
-4. Use Grep only for exact string searches if needed
-5. Synthesize findings into a clear summary
+Do NOT silently fall back to Grep. The orchestrator needs to know grepai is not working.
 `;
 
   writeFileSync(agentPath, content);
   console.log("✓ Agent deep-explore instalado em .claude/agents/deep-explore.md");
+}
+
+// Ensure grepai Bash permissions exist in the target project's .claude/settings.local.json
+function ensureGrepaiPermissions(): void {
+  const settingsPath = join(process.cwd(), ".claude", "settings.local.json");
+  const claudeDir = join(process.cwd(), ".claude");
+
+  if (!existsSync(claudeDir)) {
+    mkdirSync(claudeDir, { recursive: true });
+  }
+
+  const requiredPermissions = [
+    "Bash(grepai search:*)",
+    "Bash(grepai trace:*)",
+    "Bash(grepai:*)",
+  ];
+
+  let settings: { permissions?: { allow?: string[] } } = {};
+
+  if (existsSync(settingsPath)) {
+    try {
+      settings = JSON.parse(readFileSync(settingsPath, "utf-8"));
+    } catch {
+      settings = {};
+    }
+  }
+
+  if (!settings.permissions) settings.permissions = {};
+  if (!settings.permissions.allow) settings.permissions.allow = [];
+
+  let added = false;
+  for (const perm of requiredPermissions) {
+    if (!settings.permissions.allow.includes(perm)) {
+      settings.permissions.allow.push(perm);
+      added = true;
+    }
+  }
+
+  if (added) {
+    writeFileSync(settingsPath, JSON.stringify(settings, null, 2) + "\n");
+    console.log("✓ Permissoes de grepai adicionadas em .claude/settings.local.json");
+  }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codexa/cli",
-  "version": "8.6.11",
+  "version": "8.6.13",
   "description": "Orchestrated workflow system for Claude Code - manages feature development through parallel subagents with structured phases, gates, and quality enforcement.",
   "type": "module",
   "bin": {