Update server.js

server.js

@@ -62,15 +62,66 @@ const ALLOWED_CMDS = [
 ];
 
 const COMMANDS_REFERENCE = `
-SHELL COMMANDS (cwd=/home):
-ls, find, cat, head -n N, tail -n N, sed -n 'X,Yp', grep -n, grep -C3, grep -rn
-sed -i 's/old/new/g', node --check file.js, wc -l, diff, stat
-
-RULES:
-1. grep context before any edit
-2. node --check before+after edits
-3. match existing code style
-4. surgical sed-i on specific lines
+=== SHELL COMMANDS AVAILABLE (cwd = /home) ===
+
+FILE EXPLORATION:
+  ls -l                           List files & directories
+  find . -name "*.js"             Find JS files recursively
+  find . -name "*.json"           Find config files
+  file filename                   Show file type
+  stat filename                   File metadata (size, dates)
+
+READING CONTENT:
+  cat file                        Read entire file
+  head -n N file                  First N lines
+  tail -n N file                  Last N lines
+  sed -n 'X,Yp' file              Lines X to Y (surgical)
+  head -c N file                  First N bytes
+  grep -n "pattern" file          Lines matching pattern (with line numbers)
+  grep -A5 "pattern" file         Pattern + 5 lines after
+  grep -B3 "pattern" file         Pattern + 3 lines before
+  grep -C3 "pattern" file         Pattern + 3 lines context (before+after)
+  grep -rn "pattern" .            Recursive search all files
+
+COUNTING / STATS:
+  wc -l file                      Count lines
+  grep -c "pattern" file          Count occurrences
+  awk 'END{print NR}' file        Alternative line count
+
+EDITING (surgical, safe):
+  sed -i 's/old/new/g' file       Replace ALL occurrences
+  sed -i '12s/old/new/' file      Replace on line 12 ONLY
+  sed -i 'X,Ys/old/new/g' file    Replace in lines X-Y
+  awk '/pattern/' file            Extract matching lines
+  cut -d',' -f2 file              Extract 2nd CSV column
+  tr 'a-z' 'A-Z'                  Transform chars
+
+COMPARING:
+  diff old.js new.js              Show differences between files
+  patch file < patchfile          Apply a patch file
+
+SYNTAX / ERROR CHECKING:
+  node --check file.js            JavaScript syntax validation
+  npm test                        Run project tests
+
+PROJECT INFO:
+  cat package.json                Show project dependencies
+  npm run scriptname              Run npm scripts
+
+UTILITIES:
+  echo "text"                     Print text
+  sort file                       Sort lines alphabetically
+  uniq file                       Remove duplicate lines
+
+=== AGENT RULES ===
+1. ALWAYS run "node --check file.js" BEFORE any edit
+2. ALWAYS run "node --check file.js" AFTER any edit
+3. Use grep -C3 to understand context BEFORE inserting new code
+4. Match existing code style - grep for similar patterns first
+5. Use sed -n 'X,Yp' to read specific sections before modifying them
+6. Back up important sections mentally before sed -i changes
+7. For adding new features: grep for existing similar features first
+===============================================
 `;
 
 // ── Multer ─────────────────────────────────────────────────────────────────
@@ -443,13 +494,38 @@ Return ONLY valid JSON (no markdown):
     const smartCtx = getSmartContext(fileContent, message);
 
     const masterPlanRaw = await callAI(
-      `You are Cryo - a sharp developer AI agent on code files.
+      `You are Cryo - a razor-sharp developer AI agent operating on code files.
+You use shell commands to explore, understand, then modify code.
+
 ${COMMANDS_REFERENCE}
+
+WORKFLOW FOR EDITS:
+1. EXPLORE: grep for existing patterns similar to what user wants
+2. LOCATE: find exact line numbers (grep -n, wc -l, sed -n to read sections)
+3. UNDERSTAND: read context around insertion points (grep -C5)
+4. CHECK: node --check before any edit
+5. EDIT: surgical sed -i on specific lines
+6. VERIFY: node --check after edit
+
+WORKFLOW FOR QUERIES:
+1. grep for relevant functions/patterns
+2. read surrounding context
+3. answer precisely
+
 File: ${filePath} (${fileLines} lines)
-Preview:\n${smartCtx.substring(0, 1800)}
-${pendingTasks.length > 0 ? `PENDING TASKS:\n${pendingTasks.map(t => `  - ${t.task}`).join("\n")}\n` : ""}
-Respond ONLY with valid JSON:
-{"task_type":"query"|"edit"|"create","status":"brief description","tasks":[{"task":"name","done":false}],"commands":["cmd1"],"reasoning":"why"}`,
+Current content preview:
+${smartCtx.substring(0, 2500)}
+
+${pendingTasks.length > 0 ? `UNFINISHED TASKS FROM LAST SESSION:\n${pendingTasks.map(t => `  - ${t.task}`).join("\n")}\n` : ""}
+
+Respond ONLY with valid JSON (no markdown):
+{
+  "task_type": "query" | "edit" | "create",
+  "status": "brief description shown to user",
+  "tasks": [{"task": "subtask name", "done": false}],
+  "commands": ["cmd1", "cmd2"],
+  "reasoning": "why these commands in this order"
+}`,
       message,
       modelKey
     );
@@ -511,7 +587,7 @@ Respond ONLY with valid JSON:
             modelKey
           );
           const ans = parseJSON(ansRaw);
-          send("message", { text: ans?.answer || "No answer generated." });
+          send("message", { text: ans?.answer || ansRaw || "No answer generated." });
         }
       } else {
         const ansRaw = await callAI(
@@ -520,7 +596,7 @@ Respond ONLY with valid JSON:
           modelKey
         );
         const ans = parseJSON(ansRaw);
-        send("message", { text: ans?.answer || "No answer generated." });
+        send("message", { text: ans?.answer || ansRaw || "No answer generated." });
       }
 
     } else {