bitterbot 1.7.0 → 1.9.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -65,14 +65,14 @@ Talk through the **Control UI, WhatsApp, Telegram, Discord, Signal, Slack, or em
65
65
 
66
66
  ## Quick Start
67
67
 
68
- Pick the path that fits your machine. Each one ends in the same setup wizard, which asks for a model key, offers web search, and opens the Control UI at **[http://127.0.0.1:19001](http://127.0.0.1:19001)**.
69
-
70
- **Laptop or desktop (macOS on Apple silicon or Intel, Linux x64/arm64).** The recommended path: a signed prebuilt release with its own Node runtime. No Node, no sudo, nothing else to install:
68
+ One command. Paste it into a terminal on macOS (Apple silicon or Intel) or Linux (x64/arm64) and it takes you straight into setup:
71
69
 
72
70
  ```bash
73
71
  curl -fsSL https://github.com/Bitterbot-AI/bitterbot-desktop/releases/latest/download/install.sh | bash
74
72
  ```
75
73
 
74
+ It downloads a signed release with its own Node runtime (no Node, no `sudo`, nothing else to install), verifies it, and runs the setup wizard, which asks for a model key, offers web search, and opens the Control UI at **[http://127.0.0.1:19001](http://127.0.0.1:19001)**. What it verifies, and how to pin, roll back, or remove: [install script guide](docs/start/install-script.md).
75
+
76
76
  **Windows:** open **PowerShell** (not Ubuntu/WSL) and run this. It installs inside WSL2 for you (no administrator rights needed once WSL2 is set up):
77
77
 
78
78
  ```powershell
@@ -81,16 +81,6 @@ irm https://raw.githubusercontent.com/Bitterbot-AI/bitterbot-desktop/main/script
81
81
 
82
82
  Already in an Ubuntu/WSL terminal? Use the macOS/Linux line instead, and run it from your Linux home (`cd ~`), not from `/mnt/c`.
83
83
 
84
- What the installer verifies, and how to pin, roll back, or remove: [install script guide](docs/start/install-script.md).
85
-
86
- **Prefer npm?** Any Node 18 or newer works:
87
-
88
- ```bash
89
- npm install -g bitterbot && bitterbot onboard
90
- ```
91
-
92
- The npm package is a small launcher: it installs in seconds with no dependencies and no warnings, and on first run downloads the same signed release as the installer (about 410 MB). Never use `sudo` with it; if npm says `EACCES`, see [npm package](docs/start/npm.md#eacces-permission-denied).
93
-
94
84
  **Server (Docker).** The compose file is attached to every release:
95
85
 
96
86
  ```bash
@@ -101,6 +91,8 @@ docker compose up -d
101
91
 
102
92
  Get the gateway token with `docker compose exec -u node bitterbot-gateway node bitterbot.mjs config get gateway.auth.token` (or use your `BITTERBOT_GATEWAY_TOKEN`), then open `http://127.0.0.1:19001`. Fly.io and VPS templates: [Docker guide](docs/platforms/docker.md).
103
93
 
94
+ **Already manage Node with nvm, fnm, Volta or Homebrew?** Then `npm install -g bitterbot && bitterbot onboard` works too (Node 18 or newer); the package is a small launcher that downloads the same signed release on first run. Never run it with `sudo`. With Node from nodejs.org or from `apt`, npm cannot write to its global folder and fails with `EACCES`; the fix is the one command above, not `sudo`. Details: [npm package](docs/start/npm.md).
95
+
104
96
  **Developing Bitterbot.** Install from source with pnpm, below.
105
97
 
106
98
  **Make your first conversation personal:**
@@ -303,7 +295,7 @@ In a source checkout use `pnpm bitterbot doctor`; in Docker, `docker compose exe
303
295
 
304
296
  - **Control UI shows "Disconnected" or the first-run screen.** Open the UI at `http://127.0.0.1:19001` on the gateway machine, or through an SSH tunnel to it: the token handoff only works over loopback.
305
297
  - **Port 19001 already in use.** Another gateway is running. Find it with `ss -tlnp | grep 19001` (Linux) or `lsof -i :19001` (macOS), or start on another port with `BITTERBOT_GATEWAY_PORT=19002`.
306
- - **`npm install -g bitterbot` fails with `EACCES`.** Do not use `sudo`. Give npm a prefix you own (`npm config set prefix ~/.npm-global`), or use the installer one-liner instead: [fix it step by step](docs/start/npm.md#eacces-permission-denied).
298
+ - **`npm install -g bitterbot` fails with `EACCES`.** Your npm cannot write to its global folder (normal with Node from nodejs.org or `apt`). Do not use `sudo`. Run the one command from Quick Start instead; it needs no npm. If you must stay on npm: [give npm a folder you own](docs/start/npm.md#eacces-permission-denied).
307
299
  - **"Orchestrator binary NOT FOUND".** No prebuilt P2P orchestrator was available for your platform. Build it with `cargo build --release --manifest-path orchestrator/Cargo.toml` from a checkout.
308
300
  - **P2P peers not connecting.** The P2P Network section of `bitterbot doctor` shows whether bootstrap DNS resolves and the fallback peer is reachable; firewall problems show up there.
309
301
 
package/bitterbot.mjs CHANGED
@@ -1,5 +1,5 @@
1
1
  #!/usr/bin/env node
2
- // bitterbot 1.7.0 launcher: installs the signed release tarball on
2
+ // bitterbot 1.9.0 launcher: installs the signed release tarball on
3
3
  // first run, then runs it. Source: src/launcher/ in
4
4
  // https://github.com/Bitterbot-AI/bitterbot-desktop (built by scripts/npm-package.ts).
5
5
 
@@ -1739,7 +1739,7 @@ function launcherFile() {
1739
1739
  return null;
1740
1740
  }
1741
1741
  }
1742
- var version = true ? "1.7.0" : "0.0.0";
1742
+ var version = true ? "1.9.0" : "0.0.0";
1743
1743
  runLauncher({
1744
1744
  argv: process.argv.slice(2),
1745
1745
  env: process.env,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bitterbot",
3
- "version": "1.7.0",
3
+ "version": "1.9.0",
4
4
  "description": "Personal AI with living memory, dreaming, curiosity, and multi-channel messaging",
5
5
  "keywords": [
6
6
  "a2a",