open-agents-ai 0.187.477 → 0.187.479

package/dist/index.js

@@ -512194,17 +512194,18 @@ function buildStagnationDiagnostic(signals) {
     ``,
     `2. STATE A HYPOTHESIS in writing — what specifically is wrong? "I think X is failing because Y." Be concrete. Do NOT propose a fix yet.`,
     ``,
-    `3. VERIFY ONE ASSUMPTION — pick the ONE thing you most BELIEVE to be true and test it with the smallest possible command:`,
-    `     • If you think a package is installed: ls node_modules/<name>/package.json`,
-    `     • If you think an env var is set: printenv <NAME>`,
-    `     • If you think a file imports correctly: head -5 <file>`,
-    `     • If you don't know what an error means: web_search("<exact error string>")`,
+    `3. VERIFY ONE ASSUMPTION — pick the ONE thing you most BELIEVE to be true and test it with the smallest possible command native to whatever ecosystem you're in. Examples of the *shape* (not the exact commands):`,
+    `     • Is this artifact present on disk? (one read of the path)`,
+    `     • Does this import / reference resolve? (read 5 lines around it)`,
+    `     • Is this environment value set? (one query)`,
+    `     • Is this binary on PATH? (one which/where)`,
+    `     • Don't know what an error means? web_search("<exact error string>")`,
     ``,
-    `4. CHECK SILENT FAILURES — npm install reporting "added N packages" does NOT mean ALL declared deps installed; npm sometimes drops packages with peer-dep conflicts without erroring. Verify each expected dep individually.`,
+    `4. CHECK SILENT FAILURES — package managers and build systems frequently report "success" while silently dropping artifacts you needed. Don't trust summary output ("added N", "build complete") without verifying the SPECIFIC artifact exists.`,
     ``,
     `DO NOT in your next response:`,
     `  • Try another version, flag, or variant of any command in the list above`,
-    `  • Wipe node_modules / re-install — that hides the original error`,
+    `  • Wipe caches / re-install / re-build — that hides the original error`,
     `  • Call task_complete — being stuck on a debug problem is NEVER grounds for task_complete`,
     ``,
     `task_complete is ONLY for actual completion or unrecoverable hardware/permission errors. You are stuck on a fixable problem; diagnose it.`
@@ -518337,10 +518338,8 @@ function detectTaskMode(task) {
     return true;
   if (/(\/[\w.-]+){2,}/.test(task.slice(0, 2e3)))
     return true;
-  if (/\b(implement|build|create|refactor|write|fix|migrate|deploy|generate|setup|set up|develop|design|integrate)\b/.test(head)) {
-    if (/\b(spec|file|module|component|api|endpoint|database|schema|test|build|next\.js|typescript|react|prisma|tailwind|sql|python|rust|go)\b/.test(head)) {
-      return true;
-    }
+  if (/\b(implement|build|create|refactor|rewrite|fix|migrate|deploy|generate|setup|set up|develop|design|integrate|configure|install|debug|port|extend|add)\b/.test(head)) {
+    return true;
   }
   return false;
 }
@@ -518353,23 +518352,11 @@ function slimSystemPromptForTaskMode(prompt) {
     /^##\s*Self-Awareness( & Introspection)?\s*$/im,
     /^##\s*Debugging\s*[—-]\s*Observe Before Reasoning\s*$/im
   ];
-  const TOOL_LINES_TO_REMOVE = [
-    /^- nexus:.*$/im,
-    /^- background_run.*task_status.*task_output.*task_stop:.*$/im,
-    /^- (asr_listen|audio_capture|audio_playback|audio_analyze|camera_capture|desktop_click|bluetooth_scan|browser_action):.*$/im,
-    /^Voice\/TTS:.*$/im,
-    /^- Voice\/TTS:.*$/im,
-    /^- Desktop\/Vision:.*$/im,
-    /^- P2P:.*$/im
-  ];
   const CHAT_MODE_BLOCK = /^\*\*CHAT MODE\*\*[\s\S]*?(?=\*\*TASK MODE\*\*)/im;
   let out = prompt;
   for (const re of SECTION_HEADERS_TO_REMOVE) {
     out = out.replace(new RegExp(re.source + "[\\s\\S]*?(?=^##\\s|\\Z)", "im"), "");
   }
-  for (const re of TOOL_LINES_TO_REMOVE) {
-    out = out.replace(re, "");
-  }
   out = out.replace(CHAT_MODE_BLOCK, "");
   out = out.replace(/^\*\*TASK MODE\*\*[^\n]*\n/im, "");
   out = out.replace(/\n{3,}/g, "\n\n");
@@ -525012,7 +524999,11 @@ ${transcript}`
           /\buse\s+(\w+)/g,
           /\bcall\s+(\w+)/g,
           /`([a-z_]+)`/g,
-          /\btool[:\s]+(\w+)/g
+          /\btool[:\s]+(\w+)/g,
+          // Function-call syntax: `name(args)` is the strongest call-site signal
+          // a name can have. A bare identifier mention isn't enough — that catches
+          // filesystem nouns like `node_modules` or `package_lock`.
+          /\b([a-z][a-z0-9_]*[a-z0-9])\s*\(/g
         ];
         const contextualNames = /* @__PURE__ */ new Set();
         for (const pat of TOOL_CONTEXT_PATTERNS) {
@@ -525023,14 +525014,6 @@ ${transcript}`
               contextualNames.add(name10);
           }
         }
-        const nameCounts = /* @__PURE__ */ new Map();
-        for (const name10 of referenced) {
-          const escaped = name10.replace(/[.*+?^${}()|[\]\\]/g, "\\$&");
-          const occurrences = (systemPrompt.match(new RegExp(`\\b${escaped}\\b`, "g")) ?? []).length;
-          nameCounts.set(name10, occurrences);
-          if (occurrences >= 2)
-            contextualNames.add(name10);
-        }
         const IGNORE_LIST = /* @__PURE__ */ new Set([
           "tool_use",
           "tool_call",
@@ -525075,7 +525058,6 @@ ${transcript}`
           // reserved status for partial-done todos
           "not_started",
           // alternative status phrasing
-          // Shell/bash idioms that look like snake_case
           "ctrl_c",
           "ctrl_d"
         ]);

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "open-agents-ai",
-  "version": "0.187.477",
+  "version": "0.187.479",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "open-agents-ai",
-      "version": "0.187.477",
+      "version": "0.187.479",
       "hasInstallScript": true,
       "license": "CC-BY-NC-4.0",
       "dependencies": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "open-agents-ai",
-  "version": "0.187.477",
+  "version": "0.187.479",
   "description": "AI coding agent powered by open-source models (Ollama/vLLM) — interactive TUI with agentic tool-calling loop",
   "type": "module",
   "main": "./dist/index.js",

package/prompts/agentic/system-large.md

@@ -169,17 +169,17 @@ If you have tried 2+ approaches to the same blocker and both failed, **STOP atte
 
 **The diagnostic loop (one cycle per turn, NOT batched):**
 
-1. **READ THE FULL ERROR** — re-read the most recent failure output ENTIRELY. Don't skim the first 200 chars. If output is in a log packet, use `log_explore` with `op="errors"`, then `op="lines"` for context.
-2. **VERIFY ONE ASSUMPTION** — pick ONE thing you BELIEVE to be true and test it with the smallest possible command (e.g. "I think tailwindcss is installed" → `ls node_modules/tailwindcss/package.json`).
-3. **STATE A HYPOTHESIS in writing** before your next action. Then design ONE experiment that would CONFIRM or REFUTE it (not fix it — verify it first).
+1. **READ THE FULL ERROR** — re-read the most recent failure output ENTIRELY. If it's in a log packet, query `op="errors"` then `op="lines"` for context.
+2. **VERIFY ONE ASSUMPTION** — pick ONE thing you BELIEVE to be true and test it with the smallest possible command native to your ecosystem. Examples of the shape: "is this artifact present?", "does this import resolve?", "is this env var set?". One read, one fact verified.
+3. **STATE A HYPOTHESIS in writing** before your next action. Then design ONE experiment that CONFIRMS or REFUTES it — verify, do NOT fix yet.
 4. **WEB SEARCH the exact error message** if you don't know what it means. A 30-second lookup beats 10 retry attempts.
-5. **CHECK THE OBVIOUS** — silent failures are common. `npm install` reporting "added 141 packages" doesn't mean ALL declared deps installed; npm sometimes drops packages with peer-dep conflicts without erroring. Verify each expected dep with `ls node_modules/<name>/package.json`.
+5. **CHECK THE OBVIOUS** — package managers and build systems frequently report "success" while silently dropping artifacts. Don't trust summary output ("added N", "build complete") without verifying the SPECIFIC artifact you needed actually exists.
 6. Only AFTER root cause is verified, attempt ONE fix targeting that cause. If the fix fails, return to step 1 with the new error.
 
 **What diagnostic mode is NOT:**
-- Trying another version (`tailwindcss@3.4.19` after `tailwindcss@4.0.0`) — that's variant-fatigue, not diagnosis.
-- Adding `--force` or `--legacy-peer-deps` — those mask root causes.
-- Wiping node_modules and re-installing — hides the original error.
+- Trying another version of the same dependency after one failed — variant-fatigue, not diagnosis.
+- Adding force/override flags that suppress warnings — masks root causes.
+- Wiping caches/dependencies and reinstalling — hides the original error.
 - Calling task_complete to escape — task_complete is NEVER the answer to a stuck debugging session.
 - Use grep_search and find_files for efficient exploration (don't dump entire directories)
 - Use file_edit for small changes instead of rewriting entire files

package/prompts/agentic/system-medium.md

@@ -102,27 +102,22 @@ If you have tried 2+ approaches to the same blocker and both failed, **STOP atte
 
 **The diagnostic loop (one cycle per turn, NOT batched):**
 
-1. **READ THE FULL ERROR** — re-read the most recent failure output ENTIRELY. Don't skim the first 200 chars. If the output is in a log packet, use `log_explore` with `op="errors"` to see every marker, then `op="lines"` for surrounding context.
+1. **READ THE FULL ERROR** — re-read the most recent failure output ENTIRELY. Don't skim the first 200 chars. If the output is in a log packet, query it with `op="errors"` then `op="lines"` for surrounding context.
 
-2. **VERIFY ONE ASSUMPTION** — pick ONE thing you BELIEVE to be true and test it with the smallest possible command:
-   - "I think tailwindcss is installed" → `ls node_modules/tailwindcss/package.json` (one line)
-   - "I think the import path is right" → `cat src/lib/x.ts | head -5`
-   - "I think the env var is set" → `printenv VAR_NAME`
+2. **VERIFY ONE ASSUMPTION** — pick ONE thing you BELIEVE to be true and test it with the smallest possible command native to whatever ecosystem you're in. Examples of the *shape* (not the exact commands): "is this artifact present on disk?", "does this import resolve?", "is this environment variable set?", "does this binary exist on PATH?". One read, one fact verified.
 
-3. **STATE A HYPOTHESIS in writing** before your next action:
-   - "Hypothesis: tailwindcss didn't install because @tailwindcss/postcss has a peer-dep conflict with autoprefixer."
-   - Then design ONE experiment that would CONFIRM or REFUTE it (not fix it — verify it first).
+3. **STATE A HYPOTHESIS in writing** before your next action — "I think X is failing because Y." Be concrete. Then design ONE experiment that would CONFIRM or REFUTE it (verify it first; do NOT fix yet).
 
-4. **WEB SEARCH the exact error message** if you don't know what it means. `web_search("exact error string from terminal")`. A 30-second lookup beats 10 retry attempts.
+4. **WEB SEARCH the exact error message** if you don't know what it means. Quote the exact error string. A 30-second lookup beats 10 retry attempts.
 
-5. **CHECK THE OBVIOUS** — silent failures are common. `npm install` saying "added 141 packages" doesn't mean ALL declared deps installed; npm sometimes drops packages with peer-dep conflicts without erroring. Verify each expected dep with `ls node_modules/<name>/package.json`.
+5. **CHECK THE OBVIOUS** — package managers and build systems frequently report "success" while silently dropping artifacts. Don't trust a summary like "added N packages" or "build complete" without verifying the SPECIFIC artifact you needed actually exists. Check each expected output explicitly.
 
 6. Only AFTER root cause is verified, attempt ONE fix targeting that cause. If the fix fails, return to step 1 with the new error.
 
 **What diagnostic mode is NOT:**
-- Trying another version (`tailwindcss@3.4.19` after `tailwindcss@4.0.0` failed) — that's variant-fatigue, not diagnosis.
-- Adding `--force` or `--legacy-peer-deps` — those mask root causes, they don't reveal them.
-- Wiping node_modules and re-installing — that just hides the original error.
+- Trying a different version of the same dependency after one failed — that's variant-fatigue, not diagnosis.
+- Adding force/override flags that suppress warnings — those mask root causes, they don't reveal them.
+- Wiping caches/dependencies and reinstalling — that hides the original error.
 - Calling task_complete to escape — task_complete is NEVER the answer to a stuck debugging session.
 - Do NOT output long explanations. Focus on tool calls.
 - If file_read/list_directory returns ENOENT, use list_directory on the project root — do NOT guess parent paths