sapper-iq 1.0.4 → 1.0.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sapper-iq",
-  "version": "1.0.4",
+  "version": "1.0.6",
   "description": "AI-powered development assistant that executes commands and builds projects",
   "main": "sapper.mjs",
   "bin": {

package/sapper copy.mjs

@@ -234,24 +234,16 @@ async function runSapper() {
 
 **CRITICAL - Tool Format Rules:**
 - NEVER use JSON format
-- ONLY use this EXACT format for tools: [TOOL:TYPE:path]content[/TOOL]
-- For single-line content: [TOOL:TYPE:path:content] (legacy format still supported)
+- ONLY use this EXACT format for tools: [TOOL:TYPE:path:content]
 - Types: SHELL, READ, WRITE, MKDIR, LIST, SEARCH
 
 **Examples:**
-[TOOL:SHELL:npm install][/TOOL]
-[TOOL:READ:./package.json][/TOOL]
-[TOOL:WRITE:./app.js]console.log('hello')[/TOOL]
-[TOOL:MKDIR:./src/components][/TOOL]
-[TOOL:LIST:./src][/TOOL]
-[TOOL:SEARCH:function myFunction][/TOOL]
-
-**For multi-line content (like markdown files):**
-[TOOL:WRITE:./file.md]
-Multi-line
-content here
-with - [ ] checkboxes
-[/TOOL]
+[TOOL:SHELL:npm install]
+[TOOL:READ:./package.json]
+[TOOL:WRITE:./app.js:console.log('hello')]
+[TOOL:MKDIR:./src/components]
+[TOOL:LIST:./src]
+[TOOL:SEARCH:function myFunction]
 
 **Shell Command Rules:**
 - For operations in a specific directory, chain with cd: cd /path/to/project && npm install
@@ -416,18 +408,7 @@ with - [ ] checkboxes
         messages.push({ role: 'assistant', content: msg });
 
         const summaryMatch = msg.match(/\[SUMMARY:(.*?)\]/s);
-        
-        // Support both formats:
-        // New: [TOOL:TYPE:path]content[/TOOL] (handles multi-line content with brackets)
-        // Old: [TOOL:TYPE:path:content] (for backward compatibility)
-        const newFormatMatches = [...msg.matchAll(/\[TOOL:(\w+):([^\]]+)\]([\s\S]*?)\[\/TOOL\]/g)];
-        const oldFormatMatches = [...msg.matchAll(/\[TOOL:(\w+):([^:\]]+):([^\]]+)\]/g)];
-        
-        // Normalize to unified format: [fullMatch, type, path, content]
-        const toolMatches = [
-          ...newFormatMatches.map(m => [m[0], m[1], m[2], m[3]]),
-          ...oldFormatMatches.map(m => [m[0], m[1], m[2], m[3]])
-        ];
+        const toolMatches = [...msg.matchAll(/\[TOOL:(\w+):([^:\]]+):?([\s\S]*?)\]/g)];
 
         if (summaryMatch) {
           console.log(chalk.green.bold("\n✅ MISSION COMPLETE:"));
@@ -469,7 +450,7 @@ with - [ ] checkboxes
             break;
           }
         } else {
-          const planMatch = msg.match(/\[PLAN:([\s\S]*?)\]/) || msg.match(/\[PLAN\]([\s\S]*?)\[\/PLAN\]/);
+          const planMatch = msg.match(/\[PLAN:(.*?)\]/);
           if (planMatch) {
             const feedback = await safeQuestion(chalk.yellow('\nModify plan or type "go": '));
             if (feedback.toLowerCase() === '/stop') { active = false; break; }

package/sapper.mjs

@@ -230,57 +230,66 @@ async function runSapper() {
   if (messages.length === 0) {
     messages = [{
       role: 'system',
-      content: `You are Sapper, a senior software engineer AI assistant.
-
-**CRITICAL - Tool Format Rules:**
-- NEVER use JSON format
-- ONLY use this EXACT format for tools: [TOOL:TYPE:path]content[/TOOL]
-- For single-line content: [TOOL:TYPE:path:content] (legacy format still supported)
-- Types: SHELL, READ, WRITE, MKDIR, LIST, SEARCH
-
-**Examples:**
-[TOOL:SHELL:npm install][/TOOL]
-[TOOL:READ:./package.json][/TOOL]
-[TOOL:WRITE:./app.js]console.log('hello')[/TOOL]
-[TOOL:MKDIR:./src/components][/TOOL]
-[TOOL:LIST:./src][/TOOL]
-[TOOL:SEARCH:function myFunction][/TOOL]
-
-**For multi-line content (like markdown files):**
-[TOOL:WRITE:./file.md]
-Multi-line
-content here
-with - [ ] checkboxes
+      content: `You are Sapper, a senior software engineer AI assistant. Your PRIMARY function is to EXECUTE ACTIONS, not explain them.
+
+**CRITICAL INSTRUCTION: EXECUTE TOOLS IMMEDIATELY**
+When the user asks you to do something, DO IT using tools - don't explain how to do it.
+- ❌ WRONG: "To analyze the files, you would use [TOOL:LIST]..."
+- ✅ CORRECT: Immediately execute [TOOL:LIST]./[/TOOL] and analyze results
+
+**TOOL FORMAT (Version 1.0.5+):**
+[TOOL:TYPE]path]content[/TOOL]
+
+**Available Tools:**
+- SHELL: Execute commands
+- READ: Read file contents  
+- WRITE: Create/update files
+- MKDIR: Create directories
+- LIST: List directory contents
+- SEARCH: Search for patterns
+
+**FORMAT EXAMPLES:**
+[TOOL:SHELL]npm install[/TOOL]
+[TOOL:READ]./package.json[/TOOL]
+[TOOL:WRITE]./app.js]console.log('hello')[/TOOL]
+[TOOL:MKDIR]./src/components[/TOOL]
+[TOOL:LIST]./src[/TOOL]
+[TOOL:SEARCH]function myFunction[/TOOL]
+
+**Multi-line content:**
+[TOOL:WRITE]./README.md]
+# Title
+- [ ] checkbox
+- [x] done
+Arrays: [1, 2, 3]
 [/TOOL]
 
-**Shell Command Rules:**
-- For operations in a specific directory, chain with cd: cd /path/to/project && npm install
-- Use && to chain commands that depend on each other
-- Use | for pipes and > for redirects
-- Use relative paths after cd into a directory
-- Chain multiple commands: cd /path && npm install && npm run dev
-- User will specify which directory to work in - always use that path
-
-**Critical for npm/npx commands:**
-- ALWAYS use non-interactive flags (--typescript, --tailwind, --eslint, --no-git, etc)
-- Create projects with non-interactive flags
-- Install dependencies with: cd /path && npm install
-- Run apps with: cd /path && npm run dev
-
-**Workflow:**
-1. For complex tasks, start with [PLAN:step1,step2,step3]
-2. Execute tools immediately using the exact format above
-3. You can provide MULTIPLE tools in one message
-4. Always end with [SUMMARY:description of what was completed]
-
-**Important:**
-- No JSON responses
-- No markdown code blocks for tools
-- Only the exact bracket format: [TOOL:TYPE:path:content]
-- User will see live command output in terminal
-- Execute all tools needed to complete the task
-- Work flexibly with ANY directory the user specifies
-- Always chain cd with your command when working in a specific directory`
+**CRITICAL: Notice the bracket placement!**
+- Path comes AFTER the colon
+- Close bracket ] after path
+- Then content
+- Then [/TOOL]
+
+**Shell Commands:**
+- Change directory with cd: [TOOL:SHELL]cd /path/to/project && npm install[/TOOL]
+- Chain commands: cd /path && npm install && npm run dev
+- Use non-interactive flags: npx create-next-app --typescript --no-git
+
+**ACTION-FIRST WORKFLOW:**
+1. User asks → You EXECUTE tools immediately
+2. For complex tasks: [PLAN:description] then execute each step
+3. Multiple tools allowed per response
+4. End with [SUMMARY:what was completed]
+
+**DO NOT:**
+- Explain tool syntax to the user
+- Show examples of what "could" be done
+- Use JSON format or markdown code blocks for tools
+- Wait for permission - execute the tools
+
+**REMEMBER:** You are an executor, not an advisor. When asked to "analyze files", immediately use [TOOL:LIST] and [TOOL:READ]. When asked to "create project", immediately use [TOOL:SHELL] with the commands. Execute first, explain after if needed.
+
+Working directory: ${process.cwd()}`
     }];
   }
 
@@ -417,17 +426,8 @@ with - [ ] checkboxes
 
         const summaryMatch = msg.match(/\[SUMMARY:(.*?)\]/s);
         
-        // Support both formats:
-        // New: [TOOL:TYPE:path]content[/TOOL] (handles multi-line content with brackets)
-        // Old: [TOOL:TYPE:path:content] (for backward compatibility)
-        const newFormatMatches = [...msg.matchAll(/\[TOOL:(\w+):([^\]]+)\]([\s\S]*?)\[\/TOOL\]/g)];
-        const oldFormatMatches = [...msg.matchAll(/\[TOOL:(\w+):([^:\]]+):([^\]]+)\]/g)];
-        
-        // Normalize to unified format: [fullMatch, type, path, content]
-        const toolMatches = [
-          ...newFormatMatches.map(m => [m[0], m[1], m[2], m[3]]),
-          ...oldFormatMatches.map(m => [m[0], m[1], m[2], m[3]])
-        ];
+        // Primary format: [TOOL:TYPE:path]content[/TOOL]
+        const toolMatches = [...msg.matchAll(/\[TOOL:(\w+)\]([^\[]+?)\]([\s\S]*?)\[\/TOOL\]/g)];
 
         if (summaryMatch) {
           console.log(chalk.green.bold("\n✅ MISSION COMPLETE:"));