naiad-cli 0.2.30 → 0.2.32

package/extensions/naiad-extension.ts

@@ -166,7 +166,7 @@ export default function (pi: ExtensionAPI) {
     // ignore parse errors
   }
   if (naiadModels.length === 0) {
-    naiadModels = [{ id: process.env.NAIAD_MODEL ?? "llama-3.1-8b", display_name: "Naiad Model" }];
+    naiadModels = [{ id: process.env.NAIAD_MODEL ?? "meta-llama/llama-3.1-8b-instruct", display_name: "Naiad Model" }];
   }
 
   // Event forwarding via HTTP callback (for interactive mode)
@@ -548,9 +548,12 @@ When you're done, provide a clear, actionable summary the caller can act on.`;
       promptSnippet:
         "Consult a powerful reasoning model for deep analysis, debugging, code review, or planning (read-only).",
       promptGuidelines: [
-        "Use the `seer` tool for complex debugging where you need to trace logic across many files, code review, architecture analysis, or planning complex refactors.",
+        "Use the `seer` tool for code reviews and architecture feedback, finding difficult bugs in codepaths that flow across many files, planning complex implementations or refactors, and answering complex technical questions that require deep reasoning.",
+        "Before attempting a multi-file refactor or debugging a subtle bug that spans several modules, consult the Seer first to get a plan.",
+        "If you find yourself uncertain about the right approach or stuck after a failed attempt, consult the Seer for an alternative point of view.",
+        "Treat the Seer's response as an advisory opinion, not a directive. After receiving the Seer's response, do an independent investigation using the Seer's opinion as a starting point, then come up with an updated approach which you should act on.",
         "The Seer cannot modify files — you act on its analysis.",
-        "Don't overuse the Seer — it's slower and more expensive than doing simple analysis yourself. Use it when the task genuinely benefits from deeper reasoning.",
+        "Do NOT use the Seer for simple file reads or searches (use read, grep, find directly), basic code modifications, or tasks you can handle yourself. It is slower and more expensive — only use it when the task genuinely benefits from deeper reasoning.",
       ],
       parameters: Type.Object({
         task: Type.String({
@@ -611,7 +614,7 @@ When you're done, provide a clear, actionable summary the caller can act on.`;
           const seerEffort = process.env.NAIAD_SEER_REASONING_EFFORT || "xhigh";
           childEnv.NAIAD_FORCE_REASONING_EFFORT = seerEffort;
 
-          const timeoutMs = parseInt(process.env.NAIAD_SEER_TIMEOUT_MS || "300000", 10) || 300000;
+          const timeoutMs = parseInt(process.env.NAIAD_SEER_TIMEOUT_MS || "600000", 10) || 600000;
 
           const result = await new Promise<string>((resolve, reject) => {
             const child = spawn(piPath, args, {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "naiad-cli",
-  "version": "0.2.30",
+  "version": "0.2.32",
   "type": "module",
   "bin": {
     "naiad": "./dist/index.js"