clawmem 0.2.4 → 0.2.5

package/AGENTS.md

@@ -636,6 +636,9 @@ Symptom: "UserPromptSubmit hook error" on context-surfacing hook (intermittent)
   → Default hook timeout is 8s (since v0.1.1). If you have an older install, re-run
     `clawmem setup hooks`. If persistent, restart the watcher: `systemctl --user restart
     clawmem-watcher.service`. Healthy memory is under 100MB — if 400MB+, restart clears it.
+  → v0.2.4 fix: hook's SQLite busy_timeout was 500ms — too tight. During A-MEM enrichment
+    or heavy indexing, watcher write locks exceed 500ms, causing SQLITE_BUSY. Raised to
+    5000ms (matches MCP server). Still completes within the 8s outer timeout.
 
 Symptom: WSL hangs or becomes unresponsive during long sessions / watcher has 100K+ FDs
   → Pre-v0.2.3: fs.watch(recursive: true) registered inotify watches on EVERY subdirectory,

package/CLAUDE.md

@@ -636,6 +636,9 @@ Symptom: "UserPromptSubmit hook error" on context-surfacing hook (intermittent)
   → Default hook timeout is 8s (since v0.1.1). If you have an older install, re-run
     `clawmem setup hooks`. If persistent, restart the watcher: `systemctl --user restart
     clawmem-watcher.service`. Healthy memory is under 100MB — if 400MB+, restart clears it.
+  → v0.2.4 fix: hook's SQLite busy_timeout was 500ms — too tight. During A-MEM enrichment
+    or heavy indexing, watcher write locks exceed 500ms, causing SQLITE_BUSY. Raised to
+    5000ms (matches MCP server). Still completes within the 8s outer timeout.
 
 Symptom: WSL hangs or becomes unresponsive during long sessions / watcher has 100K+ FDs
   → Pre-v0.2.3: fs.watch(recursive: true) registered inotify watches on EVERY subdirectory,

package/SKILL.md

@@ -642,6 +642,9 @@ Symptom: "UserPromptSubmit hook error" on context-surfacing hook (intermittent)
   -> Default hook timeout is 8s (since v0.1.1). If you have an older install, re-run
      `clawmem setup hooks`. If persistent, restart the watcher: `systemctl --user restart
      clawmem-watcher.service`. Healthy memory is under 100MB — if 400MB+, restart clears it.
+  -> v0.2.4 fix: hook's SQLite busy_timeout was 500ms — too tight. During A-MEM enrichment
+     or heavy indexing, watcher write locks exceed 500ms, causing SQLITE_BUSY. Raised to
+     5000ms (matches MCP server). Still completes within the 8s outer timeout.
 
 Symptom: WSL hangs or becomes unresponsive during long sessions / watcher has 100K+ FDs
   -> Pre-v0.2.3: fs.watch(recursive: true) registered inotify watches on EVERY subdirectory,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clawmem",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "On-device context engine and memory for AI agents. Claude Code and OpenClaw. Hooks + MCP server + hybrid RAG search.",
   "type": "module",
   "bin": {

package/src/clawmem.ts

@@ -772,7 +772,7 @@ async function cmdSurface(args: string[]) {
   if (!input) process.exit(0);
 
   // Open store: writable for both (context-surfacing writes dedupe data)
-  const s = createStore(undefined, { busyTimeout: 500 });
+  const s = createStore(undefined, { busyTimeout: 5000 });
 
   try {
     if (isBootstrap) {