pi-sage 0.2.1 → 0.2.2

package/.pi/extensions/sage/runner.ts

@@ -257,8 +257,12 @@ export async function runSageSingleShot(input: SageRunnerInput): Promise<SageRun
     throw new Error(`Sage subprocess failed (code ${String(exit.code)}): ${stderrBuffer.trim() || "no stderr"}`);
   }
 
+  if (assistantText.trim().length === 0) {
+    throw new Error(`Sage subprocess returned no assistant text (code ${String(exit.code)}): ${stderrBuffer.trim() || "no stderr"}`);
+  }
+
   return {
-    text: assistantText.trim().length > 0 ? assistantText : `Sage returned no assistant text.${EOL}${stderrBuffer.trim()}`,
+    text: assistantText,
     latencyMs,
     stopReason,
     usage,
@@ -311,6 +315,9 @@ function buildPiArgs(model: string, reasoningLevel: ReasoningLevel, cliTools: st
     "-p",
     "--no-session",
     "--no-extensions",
+    "--no-skills",
+    "--no-prompt-templates",
+    "--no-themes",
     "--model",
     model,
     "--thinking",

package/README.md

@@ -17,13 +17,13 @@ Interactive-only advisory Sage extension for Pi.
 ### Global install (all projects)
 
 ```bash
-pi install pi-sage
+pi install npm:pi-sage
 ```
 
 ### Project-local install (current project only)
 
 ```bash
-pi install -l pi-sage
+pi install -l npm:pi-sage
 ```
 
 Then in Pi run:
@@ -91,3 +91,12 @@ Project settings always override global settings for that project.
 
 Package name `sage` is already taken on npm.
 `pi-sage` is currently available and is the intended publish name.
+
+## Install troubleshooting
+
+If `pi install pi-sage` fails with a local-path error (for example `Path does not exist: .../pi-sage`), your Pi version is interpreting bare names as local paths.
+Use the explicit npm source form instead:
+
+```bash
+pi install npm:pi-sage
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-sage",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "private": false,
   "type": "module",
   "description": "Interactive-only advisory Sage extension for Pi",