@whalent/agent 0.3.83 → 0.3.88

package/README.md

@@ -19,14 +19,31 @@ npm install -g @whalent/agent --prefer-online --registry=https://registry.npmjs.
 ```
 
 Node.js 20 LTS is still the safest choice on older Linux hosts. Newer Node.js
-releases can force native `node-pty` / `better-sqlite3` fallback builds that need
-newer C++ compilers when prebuilt binaries are unavailable.
+releases can force native `node-pty` fallback builds that need newer C++
+compilers when prebuilt binaries are unavailable.
+
+`better-sqlite3` is optional. When its prebuilt binary is unavailable and local
+compilation fails, npm may print warnings, but the agent can still install and
+falls back to Codex `history.jsonl` where available.
+
+Codex SQLite history reads can use the Whalent sqlite helper when installed.
+The helper is a small Go binary cached under `~/.whalent-agent/helpers/sqlite`;
+if it is missing or cannot run, the agent falls back to optional
+`better-sqlite3`, then to `history.jsonl`. Set
+`WHALENT_SQLITE_HELPER_BASE_URL` to a release/CDN directory containing
+`sqlite-helper-0.1.2-manifest.json`, or set `WHALENT_SQLITE_HELPER_MANIFEST_URL`
+directly.
+
+By default the daemon asks Platform's release API whether `sqlite-helper` has a
+newer published version, then downloads the returned manifest. Helper releases
+are independent from daemon/npm releases and are tagged as
+`sqlite-helper-vX.Y.Z`.
 
 ### Pin `better-sqlite3` to v11
 
-`@whalent/agent` uses `better-sqlite3@12` by default so Node.js 20/22/24 are all
-in the supported range. If a specific host needs the older v11 native package,
-you can replace it after the global install:
+`@whalent/agent` uses optional `better-sqlite3@12` by default so Node.js
+20/22/24 are all in the supported range. If a specific host needs the older v11
+native package, you can replace it after the global install:
 
 ```bash
 ROOT="$(npm root -g)"