openclaw - 💡(How to fix) Fix [BUG] openclaw doctor false positive: lossless-claw node:sqlite error on Bun runtime (gateway loads fine) [1 participants]

Bug Description

OpenClaw version: v2026.3.28 Runtime: Bun 1.x (Linux arm64, VPS) Node version: v22.22.1 (also present, used by some tools)

openclaw doctor reports a false positive error for lossless-claw:

ERROR lossless-claw: failed to load plugin: ResolveMessage: No such built-in module: node:sqlite
(/home/ubuntu/.openclaw/extensions/lossless-claw/index.ts)

However, the gateway runtime loads lossless-claw correctly. Journal logs confirm:

2026-04-01T16:41:24.016+00:00 [gateway] [lcm] Plugin loaded (enabled=true, db=/home/ubuntu/.openclaw/lcm.db, threshold=0.75)
2026-04-01T16:41:24.018+00:00 [gateway] [lcm] Compaction summarization model: minimax/MiniMax-M2.7 (default)

node:sqlite is natively available in both Node.js and Bun:

$ node -e "const db = require('node:sqlite'); console.log(OK)"
node:sqlite OK

$ bun -e "import sqlite from 'node:sqlite'; console.log(OK)"
bun node:sqlite OK

Root Cause Analysis

The plugin loader uses jiti (v2.6.1, bundled with openclaw) to load TypeScript plugins. In the shouldPreferNativeJiti() function:

// auth-profiles-B5ypC5S-.js, line ~26937
function shouldPreferNativeJiti(modulePath) {
  if (typeof process.versions.bun === "string") return false;  // ← Bun detected
  // ... 
}

When Bun is detected, tryNative = false, so jiti uses Babel transpilation mode instead of Bun's native module resolution. Babel's eval'd code path does not recognize node:sqlite as a built-in Node.js module — it's treated as an external/unresolvable import.

Why the gateway works but doctor fails:

• The gateway loads lossless-claw via getJiti(safeSource)(safeSource) in a warm Bun process where jiti may be cached or behaves differently on first load
• openclaw doctor spawns a fresh jiti instance for plugin discovery — every invocation cold-starts a new jiti loader, which always hits the Babel path on Bun and fails to resolve node:sqlite

This is a regression — lossless-claw worked correctly until recently, suggesting a jiti version bump or config change broke Bun+node:sqlite compatibility in Babel mode.

Environment

• VPS: Oracle Linux 6.14.0-1018-oracle (arm64)
• Bun: 1.x (runtime for openclaw-gateway)
• Node: v22.22.1 (present for CLI tools)
• lossless-claw: v0.5.2 at ~/.openclaw/extensions/lossless-claw/
• lcm.db: 68MB, 11,644 messages, 180 summaries — active and functional

Steps to Reproduce

1. Run openclaw gateway on Bun runtime
2. Observe gateway logs: lossless-claw / lcm loads correctly ✅
3. Run openclaw doctor --non-interactive (separate CLI process)
4. Observe: ERROR lossless-claw: failed to load plugin: ResolveMessage: No such built-in module: node:sqlite

Expected Behavior

openclaw doctor should either:

• (a) Recognize that node:sqlite is available natively in Bun and not flag it as an error
• (b) Load the plugin using Bun's native ESM resolver instead of jiti's Babel path
• (c) At minimum, not show a false-positive error when the plugin is demonstrably working in the gateway

Related Issues

• #34992 — Memory search fails with "missing node:sqlite" (Node.js 22, different runtime context)
• #31677 / #33048 — mem0/SQLite bindings fail after 2026.3.1 update (jiti native bindings resolution)
• Possibly related to jiti 2.6.x + Bun incompatibility with node: protocol imports

Tags

bug, plugin-loader, jiti, bun-runtime, node-sqlite, doctor