skalpel 3.0.8 → 3.0.9

package/npm-bin/skalpel.js

@@ -298,6 +298,24 @@ function runUninstall(rest) {
     // Fallback to the old unconditional message if no summary made it back.
     process.stdout.write(`\n${ok} skalpel state removed from this machine.\n`);
   }
+
+  // Only emit the "running agents still have stale env" hint when
+  // something was actually removed (or in dry-run); on already-clean
+  // re-runs the hint adds noise without value.
+  const ranAnyCleanup = summary && !(
+    summary.rcBlocksRemoved === 0 &&
+    !summary.serviceFileRemoved &&
+    summary.userDataFilesRemoved === 0
+  );
+  if (!summary || ranAnyCleanup) {
+    process.stdout.write(
+      `${dim('Note: any open shells or running coding agents (Claude Code, Codex, ' +
+      'Cursor, etc.) still have the skalpel proxy env vars cached in their ' +
+      'environment. Open a fresh shell and restart any active agents to drop ' +
+      'them.')}\n`
+    );
+  }
+
   process.stdout.write(`${dim('To finish removal, also run:')}\n`);
   process.stdout.write(`  npm uninstall -g skalpel\n`);
   return 0;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skalpel",
-  "version": "3.0.8",
+  "version": "3.0.9",
   "description": "Skalpel — local proxy and TUI for coding agents (skalpel + skalpeld bundle).",
   "license": "Apache-2.0",
   "homepage": "https://skalpel.ai",
@@ -54,10 +54,10 @@
     "x64"
   ],
   "optionalDependencies": {
-    "@skalpelai/skalpel-darwin-arm64": "3.0.8",
-    "@skalpelai/skalpel-darwin-x64": "3.0.8",
-    "@skalpelai/skalpel-linux-arm64": "3.0.8",
-    "@skalpelai/skalpel-linux-x64": "3.0.8",
-    "@skalpelai/skalpel-win32-x64": "3.0.8"
+    "@skalpelai/skalpel-darwin-arm64": "3.0.9",
+    "@skalpelai/skalpel-darwin-x64": "3.0.9",
+    "@skalpelai/skalpel-linux-arm64": "3.0.9",
+    "@skalpelai/skalpel-linux-x64": "3.0.9",
+    "@skalpelai/skalpel-win32-x64": "3.0.9"
   }
 }

package/postinstall/index.js

@@ -226,12 +226,35 @@ function main(argv) {
     return 0;
   }
 
-  // B32: refuse to run under `npx skalpel`.
-  if (paths.isNpxInvocation()) {
-    process.stderr.write(
-      'Skalpel does not support `npx skalpel` — please run `npm i -g @skalpelai/skalpel` instead.\n'
+  // npx mode: prior to v3.0.9 we returned exit 1 here, which caused
+  // npm to roll back the cached package install — leaving an empty
+  // ~/.npm/_npx/<hash>/ dir and a silent failure that re-prompted on
+  // every subsequent `npx skalpel` call. The original reason for the
+  // gate (B32) was that paths.binPath() couldn't locate the platform
+  // binary under npx's directory layout. That was fixed in v3.0.1
+  // when binPath was rewritten to use require.resolve against the
+  // platform sub-package (see paths.js:99-116) — which works under
+  // npx, global, or local install paths uniformly.
+  //
+  // We still skip the install wizard under npx because the wizard's
+  // service-register step would bake the npx cache path
+  // (~/.npm/_npx/<hash>/...) into the OS service unit, and that path
+  // is evicted by npx's cache GC. Exit 0 instead of 1 so npm install
+  // completes and the binary becomes invokable.
+  //
+  // Uninstall, however, MUST run under npx: a user running
+  // `npx skalpel uninstall` to clean up a prior `npm install -g`
+  // would otherwise hit the same skip and have nothing happen.
+  if (paths.isNpxInvocation() && !opts.uninstall) {
+    log.info(
+      'npx mode detected — skipping install wizard (service-register / ' +
+      'env-inject would bake transient npx cache paths into your system).'
     );
-    return 1;
+    log.info(
+      'For a persistent install with daemon-on-boot and shell env vars, ' +
+      'run: `npm install -g skalpel`'
+    );
+    return 0;
   }
 
   const total = 5;