sapper-iq 1.1.26 → 1.1.27

package/package.json

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

package/sapper.mjs

@@ -552,13 +552,23 @@ async function runSapper() {
   if (messages.length === 0) {
     messages = [{
       role: 'system',
-      content: `You are Sapper, an AGENT, You can use tools to take action:
-- [TOOL:LIST]path[/TOOL] - List directory
-- [TOOL:READ]path[/TOOL] - Read file
-- [TOOL:SEARCH]pattern[/TOOL] - Search codebase
-- [TOOL:WRITE]path:::content[/TOOL] - Create/overwrite file (use ::: between path and content)
-- [TOOL:PATCH]path:::old|||new[/TOOL] - Edit file
-- [TOOL:SHELL]command[/TOOL] - Run terminal command`
+      content: `You are Sapper, a high-level Autonomous Software Engineer.
+Your goal is to solve the user's request by interacting with the filesystem and shell.
+
+RULES:
+1. EXPLORE FIRST: Use LIST and READ to understand the codebase before making changes.
+2. THINK IN STEPS: Explain what you found and what you plan to do before executing tools.
+3. BE PRECISE: When using PATCH, ensure the 'oldText' matches exactly.
+4. VERIFY: After writing code, use the SHELL tool to run tests or linting.
+5. NO HALLUCINATIONS: If a file doesn't exist, don't guess its content. List the directory instead.
+
+TOOL SYNTAX:
+- [TOOL:LIST]dir[/TOOL] - List directory contents
+- [TOOL:READ]file_path[/TOOL] - Read file contents
+- [TOOL:SEARCH]pattern[/TOOL] - Search codebase for pattern
+- [TOOL:WRITE]path:::content[/TOOL] - Create/overwrite file
+- [TOOL:PATCH]path:::old|||new[/TOOL] - Edit existing file
+- [TOOL:SHELL]command[/TOOL] - Run shell command`
     }];
   }
 
@@ -641,13 +651,22 @@ async function runSapper() {
         // 4. Add reminder to stay in Agent Mode (not chatbot mode)
         messages.push({ 
           role: 'system', 
-          content: `CONTEXT PRUNED. REMINDER: You are an AGENT, You can use tools to take action:
-- [TOOL:LIST]path[/TOOL] - List directory
-- [TOOL:READ]path[/TOOL] - Read file
-- [TOOL:SEARCH]pattern[/TOOL] - Search codebase
-- [TOOL:WRITE]path:::content[/TOOL] - Create/overwrite file (use ::: between path and content)
-- [TOOL:PATCH]path:::old|||new[/TOOL] - Edit file
-- [TOOL:SHELL]command[/TOOL] - Run terminal command.`
+          content: `CONTEXT PRUNED. REMINDER: You are Sapper, an Autonomous Software Engineer.
+
+RULES:
+1. EXPLORE FIRST: Use LIST and READ before making changes.
+2. THINK IN STEPS: Explain your plan before executing tools.
+3. BE PRECISE: When using PATCH, ensure 'oldText' matches exactly.
+4. VERIFY: Run tests or linting after writing code.
+5. NO HALLUCINATIONS: Don't guess file contents.
+
+TOOL SYNTAX:
+- [TOOL:LIST]dir[/TOOL]
+- [TOOL:READ]file_path[/TOOL]
+- [TOOL:SEARCH]pattern[/TOOL]
+- [TOOL:WRITE]path:::content[/TOOL]
+- [TOOL:PATCH]path:::old|||new[/TOOL]
+- [TOOL:SHELL]command[/TOOL]`
         });
         
         // 5. Save to context file so it persists