@bitseek/claw 1.3.4 → 1.3.5

package/dist/build-info.json

@@ -1,6 +1,6 @@
 {
-  "version": "1.3.4",
+  "version": "1.3.5",
   "upstreamVersion": "2026.3.2",
   "commit": "f31c077fff091cdd9d96badde3c917910af1f7c0",
-  "builtAt": "2026-03-22T04:44:52.677Z"
+  "builtAt": "2026-03-22T14:59:30.129Z"
 }

package/dist/canvas-host/a2ui/.bundle.hash

@@ -1 +1 @@
-0c0d26cb8628cf296a6bf5d78dba7b37a09b0a532f452fabe8d790d1e44e758b
+6986c1880f9cfa59901f8ecebbbd9a8d5bdda60be704c0b9c62228faf2d38d93

package/docs/install/installer.md

@@ -387,6 +387,13 @@ Use non-interactive flags/env vars for predictable runs.
     Run `npm config get prefix` and add that directory to your user PATH (no `\bin` suffix needed on Windows), then reopen PowerShell.
   </Accordion>
 
+  <Accordion title='Windows: "node-llama-cpp" / "ERR_DLOPEN_FAILED" during install'>
+    `node-llama-cpp` powers local embeddings and uses a native Windows binary.
+    OpenClaw can still install and run without it, but local embeddings require the Microsoft Visual C++ Redistributable runtime on the machine.
+
+    If you hit this while upgrading from an older package build, install the x64 Microsoft Visual C++ 2015-2022 Redistributable, reopen PowerShell, and rerun the installer.
+  </Accordion>
+
   <Accordion title="Windows: how to get verbose installer output">
     `install.ps1` does not currently expose a `-Verbose` switch.
     Use PowerShell tracing for script-level diagnostics:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bitseek/claw",
-  "version": "1.3.4",
+  "version": "1.3.5",
   "description": "BitSeek-branded OpenClaw distribution with a multi-channel AI gateway",
   "keywords": [],
   "homepage": "https://github.com/adv-org/bitseek-claw#readme",
@@ -252,6 +252,11 @@
     "@napi-rs/canvas": "^0.1.89",
     "node-llama-cpp": "3.16.2"
   },
+  "peerDependenciesMeta": {
+    "node-llama-cpp": {
+      "optional": true
+    }
+  },
   "engines": {
     "node": ">=22.12.0"
   },