@trybullet/cli 1.3.18 → 1.3.20

package/README.md

@@ -137,6 +137,58 @@ npm run dist     # local unsigned build (right-click → Open)
 `npm run eval:classifier` additionally checks routing quality — plan intent and
 plan-approval verdicts — against a live nano model, so it needs a provider key.
 
+## Linux
+
+Every host difference resolves in one place, `electron/platform.js`; nothing else
+in `electron/` or `src/` may hardcode a path or read `process.platform`, and
+`scripts/check-platform.sh` fails the build if it does. CI runs the suite on
+macOS and Ubuntu both.
+
+```bash
+npm run dist:linux            # AppImage + deb into release/
+npm run release:publish linux # push to the linux update feed
+```
+
+**Which package to hand a user**
+
+| | `.deb` | AppImage |
+|---|---|---|
+| Ubuntu / Debian | **recommended** | needs setup, see below |
+| Other distros | — | **recommended** |
+| Updates itself | no | yes |
+
+The split is not a preference, it is what works. Chromium's sandbox needs either
+unprivileged user namespaces or a setuid helper. Ubuntu 24.04 blocks the former
+(`kernel.apparmor_restrict_unprivileged_userns=1`) and an AppImage is mounted
+`ro,nosuid`, so the helper can never be setuid there — the app aborts on launch
+with "The SUID sandbox helper binary was found, but is not configured
+correctly." A `.deb` can make the helper setuid, which `build/deb-postinst.sh`
+does; read that file before touching it, because electron-builder's generated
+postinst gets this wrong in a way that only breaks for the user, not the
+packager. Ubuntu 24.04 also ships FUSE3, so an AppImage needs `libfuse2t64`
+before it will even mount.
+
+Running with `--no-sandbox` would paper over all of it and is deliberately not
+done: the Preview panel renders pages the agent navigated to, which is exactly
+what that sandbox is there to contain.
+
+**Two Linux gaps to know about**
+
+- **No on-device model.** node-llama-cpp kills the process while loading a model
+  inside Electron on Linux — SIGILL on Electron 32, SIGSEGV on 34 and 38 — while
+  the same model and binaries work under plain `node` on the same machine. A
+  native crash cannot be caught, so `platform.localEngine()` gates it off and
+  onboarding asks for a subscription or API key instead. Fixing it means running
+  the engine in a child node process and streaming over IPC.
+- **`.deb` cannot self-update.** electron-updater only supports AppImage on
+  Linux, so Settings tells `.deb` users where to download from rather than
+  offering a button that cannot work. A real fix is an apt repository.
+
+The AppImage ships CPU and Vulkan llama backends only; the CUDA ones are
+excluded in `build.files` because they are 526 MB and load solely where the CUDA
+runtime is already installed, which for most desktops means never. Vulkan
+already covers NVIDIA, AMD, and Intel. Re-adding them is one glob.
+
 ## Releasing
 
 Installed copies update themselves: the app checks

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trybullet/cli",
-  "version": "1.3.18",
+  "version": "1.3.20",
   "description": "The fastest coding agent — terminal edition. Same router, tools and agent loop as the Bullet desktop app, in your shell.",
   "license": "UNLICENSED",
   "homepage": "https://usebullet.com",
@@ -24,11 +24,11 @@
     "bin/bullet.js"
   ],
   "optionalDependencies": {
-    "@trybullet/cli-darwin-arm64": "1.3.18",
-    "@trybullet/cli-darwin-x64": "1.3.18",
-    "@trybullet/cli-linux-x64": "1.3.18",
-    "@trybullet/cli-linux-arm64": "1.3.18",
-    "@trybullet/cli-win32-x64": "1.3.18"
+    "@trybullet/cli-darwin-arm64": "1.3.20",
+    "@trybullet/cli-darwin-x64": "1.3.20",
+    "@trybullet/cli-linux-x64": "1.3.20",
+    "@trybullet/cli-linux-arm64": "1.3.20",
+    "@trybullet/cli-win32-x64": "1.3.20"
   },
   "engines": {
     "node": ">=18"