pando-ai 0.2.4 → 0.2.5

package/README.md

@@ -26,8 +26,11 @@ npx -y pando-ai
 
 On a terminal this opens the **firewall console**: it detects whether `codex`
 and `claude` are protected, offers to install supervised launchers for any that
-aren't, and shows current status and policy. After installation you keep running
-`codex` and `claude` normally — Pando supervises each launch.
+aren't, and shows current status and policy. It also installs a persistent
+`~/.pando/bin/pando-ai` command shim, so future commands such as
+`pando-ai uninstall` work even when the first run came from `npx`. After
+installation you keep running `codex` and `claude` normally — Pando supervises
+each launch.
 
 ## How it works
 
@@ -179,9 +182,9 @@ provider-bound gateway enforcement is disabled.
 ## Surfaces
 
 ```bash
-pando-ai                 # firewall console (TTY): status + proactive install
+pando-ai                 # firewall console (TTY): status, install, uninstall
 pando-ai install         # force a (re)install pass
-pando-ai uninstall       # remove Pando shims, managed PATH block, and install state
+pando-ai uninstall       # remove Pando shims, managed PATH block, install state, and global npm install when detected
 pando-ai serve [path]    # stdio MCP server for MCP clients
 pando-ai serve-http      # HTTP MCP server
 pando-ai gateway         # run the firewall gateway in the foreground (debug)
@@ -202,15 +205,13 @@ pando-ai uninstall
 ```
 
 This removes Pando-owned `codex`/`claude` shims from `~/.pando/bin`, removes
-the managed PATH block from your shell startup file when present, and deletes
-`~/.pando/state.json` so declined/install state does not suppress future setup
-prompts. It does not delete policy files, logs, or other user data.
-
-If you installed the npm package globally, remove it separately:
-
-```bash
-npm uninstall -g pando-ai
-```
+the Pando-owned `pando-ai` command shim, removes the managed PATH block from
+your shell startup file when present, and deletes `~/.pando/state.json` so
+declined/install state does not suppress future setup prompts. It does not
+delete policy files, logs, or other user data. If the command is running from a
+global npm install, it also removes that global `pando-ai` package
+automatically. `npx` runs are temporary, so there is no persistent npm package
+to remove in that case.
 
 ## MCP serve mode
 

package/bin/pando-ai.js

@@ -29,10 +29,30 @@ const current = parseNodeVersion(process.version);
 if (!isSupportedNode(current)) {
   const detected = current ? `${current.major}.${current.minor}.${current.patch}` : process.version;
   console.error(
-    `[pando] pando-ai requires Node.js 22.5.0 or newer. Detected ${detected}.\n` +
-      "[pando] Upgrade Node, then re-run `npx -y pando-ai`.",
+    "\n" +
+      `[pando] pando-ai requires Node.js 22.5.0 or newer. Detected ${detected}.\n` +
+      "[pando] Please update Node.js, then re-run: npx -y pando-ai\n",
   );
   process.exit(1);
 }
 
+const originalEmitWarning = process.emitWarning;
+process.emitWarning = function pandoEmitWarning(warning, ...args) {
+  const text =
+    typeof warning === "string"
+      ? warning
+      : warning && typeof warning === "object" && "message" in warning
+        ? String(warning.message)
+        : "";
+  const type = typeof args[0] === "string" ? args[0] : undefined;
+  if (
+    type === "ExperimentalWarning" ||
+    text.includes("SQLite is an experimental feature") ||
+    text.includes("localStorage is not available")
+  ) {
+    return;
+  }
+  return originalEmitWarning.call(process, warning, ...args);
+};
+
 require("../dist/cli.js");